hscloud/.bazelrc

# https://github.com/bazelbuild/rules_docker/issues/842
build --host_force_python=PY3
test --host_force_python=PY3
run --host_force_python=PY3
build --stamp
build --workspace_status_command=./bzl/workspace-status.sh
test --build_tests_only
test --test_output=errors
*: move away from python_rules python_rules is completely broken when it comes to py2/py3 support. Here, we replace it with native python rules from new Bazel versions [1] and rules_pip for PyPI dependencies [2]. rules_pip is somewhat little known and experimental, but it seems to work much better than what we had previously. We also unpin rules_docker and fix .bazelrc to force Bazel into Python 2 mode - hopefully, this repo will now work fine under operating systems where `python` is python2 (as the standard dictates). [1] - https://docs.bazel.build/versions/master/be/python.html [2] - https://github.com/apt-itude/rules_pip Change-Id: Ibd969a4266db564bf86e9c96275deffb9610dd44 2019-07-14 16:29:52 +02:00			`# https://github.com/bazelbuild/rules_docker/issues/842`
.bazelrc: switch over to PY3 (rules_docker is now fully PY3 compliant) Change-Id: I53edb8eae81779d5b8cea36e3bec4c05ca2c6e0d 2021-01-30 17:23:31 +01:00			`build --host_force_python=PY3`
			`test --host_force_python=PY3`
			`run --host_force_python=PY3`
.bazelrc: re-enable stamping in go Change-Id: Icb25fa970e090730803ff964f26e7c0dc5295fae 2020-07-30 21:47:27 +02:00			`build --stamp`
tools/workspace-status.sh -> bzl/ This is bazel-specific. Change-Id: I2592c30f4e8f5e414d2fb6cf90f36b36e069b7cb 2019-07-21 16:15:12 +02:00			`build --workspace_status_command=./bzl/workspace-status.sh`
app/gerrit/kube: implement This change impelements the k8s machinery for Gerrit. This might look somewhat complex at first, but the gist of it is: - k8s mounts etc, git, cache, db, index as RW PVs - k8s mounts a configmap containing gerrit.conf into an external directory - k8s mounts a secret containing secure.conf into an external directory - on startup, gerrit's entrypoint will copy over {gerrit,secure}.conf and start a small updater script that copies over gerrit.conf if there's any change. This should, in theory, make gerrit reload its config. This is already running on production. You're probably looking at this change through the instance deployed by itself :) Change-Id: Ida9dff721c17cf4da7fb6ccbb54d2c4024672572 2019-06-21 20:38:35 +02:00			`test --build_tests_only`
smsgw: productionize, implement kube/mirko This productionizes smsgw. We also add some jsonnet machinery to provide a unified service for Go micro/mirkoservices. This machinery provides all the nice stuff: - a deployment - a service for all your types of pots - TLS certificates for HSPKI We also update and test hspki for a new name scheme. Change-Id: I292d00f858144903cbc8fe0c1c26eb1180d636bc 2019-10-02 20:46:48 +02:00			`test --test_output=errors`