951c2f4cde
bazel likes to build everything in ~/.cache and then symlink bazel-* "convience symlinks" in the workspace/build directory. This causes a problem for building docker images where we run in the context of the build directory; docker will not follow the symlinks out of build directory. Currently the bazelisk-build copies parts of the build to the top-level; this means the bazelisk-build role is gerrit specific, rather than generic as the name implies. We modify the gerrit build step to break build output symlink and move it into the top level of the build tree, which is the context the docker build runs in later. Since this is now just a normal directory, we can copy from it at will there. This is useful in follow-on builds where we want to start copying more than just the release.war file from the build tree, e.g. polygerrit plugin output. While we're here, remove the javamelody things that were only for 2.X series gerrit, which we don't build any more. [1] https://docs.bazel.build/versions/master/output_directories.html Change-Id: I00abe437925d805bd88824d653eec38fa95e4fcd |
||
|---|---|---|
| .. | ||
| accessbot | ||
| etherpad | ||
| gerrit | ||
| gitea | ||
| gitea-init | ||
| grafana | ||
| haproxy-statsd | ||
| hound | ||
| jinja-init | ||
| jitsi-meet | ||
| python-base | ||
| python-builder | ||
| uwsgi-base | ||