943f66e3e6
To provide a stepwise upgrade path from 2.13 running directly to 2.15 in a container, make a container image containing the war we're using currently. This should let us make a change to how we run the war without changing the war at all, and then update the war. Instead of trying to make a clean build for gerrit 2.13 inside of a builder image, just have it wget the already built wars and jars we have. There are pieces of this that duplicate what's being done in puppet, but in this context it's not immediately clear these are important to do. However, it's also not clear they're a bad idea. The gerrit 2.15 build needs a newer bazel. Looking at the CI scripts that are used by gerrithub, we find that they use bazel 0.26.1 and nodesource v10. Use the bazel image published by google to get a bazel builder image. Set gerrit uid/git to 3000 in both images to match the existing directory ownership so that bindmounting doesn't face permissions problems. Change-Id: I3533f01c0859ed50640dcfd98023994c5867c056 |
||
|---|---|---|
| .. | ||
| gerrit | ||
| gitea | ||
| gitea-init | ||
| haproxy-statsd | ||
| jinja-init | ||
| python-base | ||
| python-builder | ||