Closed kr closed 7 years ago
One possible reason: maybe they don't run on CentOS 6 (glibc 2.12).
The official protobuf binaries are built with an incompatible version of glibc. What do you think of pulling the compiled binary out of the image and throwing it up on s3? We can add downloading it as a part of the image build.
Worth mentioning: although generated Go code in proto3 is not supposed to contain getters for simple scalar fields (as documented here), a recent change to protoc
re-added them. The resulting difference between go generate
output on my computer vs. that on Wercker had me briefly confounded.
Whichever version of protoc
we settle on for CI, let's make sure it's the same one we use for development.
Fixed by #893
Our docker image for CI is compiling protoc from source, which takes an ungodly amount of time. But they have binary releases we can download.
https://github.com/google/protobuf/releases
Let's look in to that.