We have a wrapper script now that works on the gerrit servers.
Run it after we run the gitea repo creation.
Remove the -it since this is not an interactive run. Add net=host
so that localhost maps. And set the server to localhost.
Don't run manage-projects in gate jobs for run-review yet, because
we don't have a functioning enough gerrit. We can follow up with
that.
Change-Id: I8c0eb5d7973815ae21d4d5bc1be8d4bdfe56d7fc
This is required because RAX have an odd /v2 that isn't listed in the
catalogue but actually exists (but isn't really full /v2/ support).
It became a problem when recent client versions dropped /v1 support,
so now we have to force them to v2 like this.
Depends-On: https://review.opendev.org/714624
Change-Id: I6f139d2b3036ef0ecaddf3a9a225faae3a2b0450
We seem to semi regularly get questions about why we don't use features
like Gitea's issue tracker and wiki. Add that to the opendev.org front
page FAQ.
Change-Id: Ie5c4602741dcdb9cc4e87b9286a8f6b8b7ed7934
For us to build gerrit images from other repos, we kind of need
system-config to be in the list of required-projects.
Change-Id: Id3712fae876cb1f8e8abf2bf0a93c781f2538287
These are useful for the times when a secret needs to be decrypted
for debugging but seem to have been deleted when we did the zuulv3
migration removal.
Change-Id: Ib1544d9032df9bd25c50eeca032f643e40f035b0
These are set in the job now, so we don't need them
here.
Depends-On: https://review.opendev.org/714306
Change-Id: I8ff79ffc0fc0ab3d914966d72fe7eb52865ecee5
Update conf.py and index.rst for OpenDev.
Use newer openstackdocstheme and update conf.py for this.
Change-Id: I62312ca1d3fda9221660b7bb664c8ea55dac68a4
We need to run these on jeepyb patches since we're
including jeepyb into gerrit images. We also need to
add jeepyb/* to the file matchers of the jobs.
Change-Id: I4479b5cef44d3c17d5c5d9412e6c1f127bf699e3
When we use these outside of system-config (like in jeepyb)
the paths are all wrong for finding the docker context. Set
zuul_work_dir on the base jobs so that it works as expected
when we trigger from other places.
Change-Id: I986fe0d12ebfb94bd81fbe3ff1ae51b6f0dd68c7
jeepyb is installed in the gerrit image because of hook scripts.
To run manage-projects and track-upstream, make wrapper scripts
in /usr/local that runs the commands from in the container image
bind-mounting the appropriate dirs and files into the container.
Change-Id: I7ef1f00e69d4c310d69d83c80ca210e8f340878d
We set core size to 0 and number of files to twice the setting of
core.packedGitOpenFiles. Make gerrit_packed_git_open_files a role
variable so we can jinja the 2x transformation.
Change-Id: I05dbfe1f091e7014c47b0f1ba79f99b51d1a6c30
This is in anticipation of running manage-projects, which wants to
use the dev subdir of project-config when run on dev, but we're
currently not doing anything with that. Point at root or dev as
appropriate. Then we can do a similar thing - probably just
bind-mounting the root or the dev when we docker run for
manage-projects.
Change-Id: Ia13bbb0bf8dbe1f7e7c0f378ba9b41bef3ecd5c1
There are two different concerns here. One is configuring the gitea
and gerrit services. This is independent from the management of
projects running inside them.
Make a manage-projects playbook which currently runs gitea-git-repos
but will also get a gerrit-git-repos role in a bit. Make a
service-gitea playbook for deploying gitea itself and update
run_all to take all of that into account. This should make our
future world of turning these into zuul jobs easier.
Add several missing files to the files matchers for run-gitea
and run-review.
Also - nothing about this has anything to do with puppet.
Change-Id: I5eaf75129d76138c61013a3a7ed7c381d567bb8b
Job dependencies are overrides, not additions, so in the case of
several jobs that have the opendev-buildset-registry job in their
depends via parent jobs but express a dependency in the pipeline
config, the dependency on opendev-buildset-registry was not there.
Add mention in the pipeline config. Remove it from the
system-config-run-gitea job definition because we're defining it
in the pipeline and it could lead to confusion.
Change-Id: I4a115a3c547b7feb34d1552278ae25337c2ae371
We don't use the bazel image anymore, so it can go away.
Also, the bouncy castle line in the gerrit base dir is bong.
Change-Id: I58842dd9adee108893c0c953c4bb8361b9117775
We install jeepyb and launchpadlib in gerrit-base. Those are
important. We also need to add cgi for gitweb.
The gerrit init command does two things that we don't actually
want it to do at runtime. It extracts the plugins into the
plugins dir, and it downloads the right database library.
We can extract the plugins for it during image creation, and
then we can also download the plugin it would have downloaded.
We can also download the mysql library for it:
https://gerrit.googlesource.com/gerrit/+/refs/heads/stable-2.13/gerrit-pgm/src/main/resources/com/google/gerrit/pgm/init/libraries.config
Finally, we tell it to not download or expand anything during
init, because we're running in a container and next time we run
the process that dir isn't going to be there.
Our gerrit integration tests don't depend on our gerrit image builds.
Put in image depends between run-review and gerrit builds.
We also need to depend directly on opendev-buildset-registry.
Add java.security.egd setting to java invocation
This tells java to be secure.
https://stackoverflow.com/questions/58991966/what-java-security-egd-option-is-for
Add support for setting heap limit properly
The gerrit init script does this based on the value in
container.javaOptions. We could, but then we'd have to
run an entrypoint script. Instead, set the value via
the JAVA_OPTIONS env var setting based on a value from
ansible.
Finally, make gerrit-master image build non-voting
It looks like there might be a real issue, but debugging that
is not important for us at this moment.
Depends-On: https://review.opendev.org/714216
Change-Id: I01e94c10f470fb3c8ddfce7b0e201357e5050679
The Airship project is continuously publishing documentation to AFS,
so serve that volume with a corresponding vhost on the static01
server. Also add it to the list of volumes for periodic vos release.
Change-Id: I718963533d9e8596d44d451b5e930314d699fa28
Depends-On: https://review.opendev.org/706599
We have a need to run ad-hoc commands with the various things
mounted, such as the gerrit init, as well as our friends like
manage-projects. Make a second "service" that doesn't do anything,
but allows us to run "docker-compose run".
Change-Id: Ic9bafe85b90af413c891b969273437be9df6a79f
We don't need to do this when we're restarting, only when we're
installing or starting for the first time.
Change-Id: If80daa5366c56e5f966c499afea4dc7b3421e79f
Starting and stopping gerrit is now done by our new docker-compose
overlord. Update the rename playbook to use it for stopping at
the beginning, and then use the start tasks of the gerrit role
to start it at the end.
Change-Id: Ibd07f9269771dfa70fbefbba69b905f165e018af
