Skip to content

Native binary build fails due to VCS stamping issues #152

@absurdfarce

Description

@absurdfarce

Noticed while working on the 0.2.0 release. Builds on multiple native platforms started failing with errors along these lines:

go: downloading github.com/alecthomas/kong v0.2.17
go: downloading github.com/datastax/go-cassandra-native-protocol v0.0.0-20220706104457-5e8aad05cf90
go: downloading github.com/hashicorp/golang-lru v0.5.4
go: downloading go.uber.org/zap v1.17.0
go: downloading gopkg.in/yaml.v2 v2.4.0
go: downloading github.com/datastax/astra-client-go/v2 v2.2.54
go: downloading github.com/google/uuid v1.3.0
go: downloading github.com/pkg/errors v0.9.1
go: downloading go.uber.org/atomic v1.8.0
go: downloading go.uber.org/multierr v1.7.0
go: downloading github.com/pierrec/lz4/v4 v4.0.3
go: downloading github.com/golang/snappy v0.0.3
go: downloading github.com/deepmap/oapi-codegen v1.12.4
go: downloading github.com/apapsch/go-jsonmerge/v2 v2.0.0
error obtaining VCS status: exit status 128
	Use -buildvcs=false to disable VCS stamping.
Error: Process completed with exit code 1.

An example can be found here. Relevant spot in the the build process is here as you can clearly see the "apt install" take place just before that in the log.

Problem here appears to stem from the upgrade to the Go version in the build. In Go 1.18 a new feature was added which embeds VCS info into the binary itself. Something in our build process is apparently causing this functionality to fail.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions