Create CI test that ensure generated files have not changed

Question

Create CI test that ensure generated files have not changed

johanbrandhorst opened this issue 7 years ago · 5 comments

It can use the scripts from gogo/googleapis as mentioned in #4 (comment).

This should include splitting the third_party folder generation assets into a separate Makefile job as it is generation-time dependant.

Answer 1 · 2018-02-25T10:44:34.000Z

Sounds good.

Are you able to create a travis job, now that you are a member of gogo?

Answer 2 · 2018-02-25T11:41:09.000Z

I added Travis to the repo but when I triggered a build it failed. I will look into it later, a bit busy today. Feel free to fix it if you know what's missing. I have no prior experience with Travis.

Answer 3 · 2018-02-25T12:08:24.000Z

Take your time.

Is there some other free builder you do have experience with?

Answer 4 · 2018-02-25T14:04:47.000Z

I use an advanced CircleCI setup to test the GopherJS gRPC-web bindings, but I want to learn to use Travis too :).

Answer 5 · 2018-02-25T14:09:35.000Z

I have heard good things about circle ci, so it is definitely an option instead of travis, but your choice.

…

On Sun, 25 Feb 2018, 15:04 Johan Brandhorst, ***@***.***> wrote: I use an advanced CircleCI setup to test the GopherJS gRPC-web bindings, but I want to learn to use Travis too :). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvsLfGubAuAJRRQN9x4uN1FDecKzpu8ks5tYWh_gaJpZM4SSPOr> .