GoogleContainerTools / GoogleContainerTools/container-structure-test
Infer bazel-bin directory in release automation
Open
good first issue
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
We should be able to infer the output directory for the binary when building with bazel, so we don't have to keep changing the hardcoded name whenever we make a change to the build process. Something like
`bazel info | grep bazel-bin | cut -d' ' -f2`
or
`bazel info bazel-bin`
should give us enough to work with.
Contributor guide
Assessment
This issue has not been assessed yet.