-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis CI failing with undefined proto errors for trivial text change PR's #377
Comments
We really need to move to a docker based build environment. |
@hakanmemisoglu: It is asking a lot, but would you be interested and willing to do this? |
@saad-ali Hakan is a bit swamped at the moment, but I have some time to help out. Do you have a preference for where to put the Dockerfile and upload an image? It looks like https://hub.docker.com/_/golang is almost enough to run the travis commands. The only thing missing is |
@tdmanv thank you very much, that would be great. Let's put it in https://quay.io/organization/k8scsi |
@saad-ali I don't mind: https://quay.io/user/tdmanv |
@tdmanv invite to the org sent! Feel free to create a new repo called |
Great thanks for the pointer. My preference would be to first merge #378, which is required no matter what and will immediately unblock the other PRs. After I can followup with dockerizing the build. It requires makefile and travis changes so it will take a bit longer. What do you think? |
SGTM. Merged 378 |
@tdmanv can you and @hakanmemisoglu also make sure to sign the CLA. I also sent you an email with instructions. |
Done! Thank you. |
Thank you! |
For example this PR is just text change: #375
CI is failing here: https://travis-ci.org/container-storage-interface/spec/jobs/569485934
The error:
My assumption is one of the proto libraries/grpc version is unpinned in CI and the golang (and some other stuff) has pinned versioning. So just every once in a while CI will break for no reason.
This is an issue with the Spec. Generating the protos on a local machine isn't much better to be honest, it's always an exercise in figuring out the correct package versions to have on my workstation...
/assign @jdef @saad-ali @jieyu @julian-hj
The text was updated successfully, but these errors were encountered: