cockroachdb / cockroachdb/cockroach-operator

Build Clean Up and Developer Effeciency

未关闭
#437 0 条评论 0 个 reaction 已指派 1 人 已被 @alinadonisa 认领 在 GitHub 查看
主要语言
Go
星标
318
派生
104
平均合并
1 天 6 小时
30 天内合并 PR
1

描述

We have default values set in multiple places. Primarily the Makefile and https://github.com/cockroachdb/cockroach-operator/blob/master/hack/build/version.sh, which is when we run bazel with `--stamp.`

Here are the main efforts with this issue:

1. Move as much as possible into bazel - release, development, scripts, etc. We need to run bazel commands to do everything, including releases.
2. Put error handling in `version.sh`
2. Move as much as possible out of the Makefile
2. Use a .bazelrc file https://docs.bazel.build/versions/master/guide.html#bazelrc-the-bazel-configuration-file to drive the effort
3. Document it
4. Test it

Have variables, such as version numbers, docker registry locations, in a `.bazelrc` file, which is not changed except with releases. We can use `--config` as well and might be able to have a single bazel config file, or we can have a developer example `.bazelrc` file and then a release `.bazelrc` file.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。