We need to log to a file and then collect it to the log output on
zuul. Default to true to that steady-state reads nicely. When we
add new jobs we should make sure to set to false first so that we
can vett the output before publishing it.
Change-Id: Ia4f759b82a5fff6e36e4284c11281254c0d5627d
If we're going to trigger this from project-config, we should
make sure it updates project-config as a first step. Currently
it's counting on having run after service-review in run_all.sh.
Change-Id: I14ce9b42af533c742128ce87cda8c8fb897632e4
Turns out our config has a bunch of hardcoded /home/gerrit2/acls
entries in it. That doesn't work if we're just pointing the
config file at /opt/project-config/gerrit/acls.
Change-Id: I387e446501e17a3bdd807807d5ef6b69b53abde5
We use this to make the .gitreview file too, so our thought that
we could just use localhost was a little misguided.
Change-Id: I501b10b2003c7e04ca1ac345d14fa33916b3e60b
We have a new base job, system-config-run-containers, that does
what is needed to ensure images are pulled from the intermediate
registry when appropriate.
Also remove opendev-buildset-registry from jobs that neither
build nor consume images from this tenant.
Change-Id: I5de4a1ddbf336749160a3ef996b6b3f55bc46666
When we run manage-projects, we always want the latest image.
Add a task file to the gerrit role so that it can have access
to role default variables. Then call it from the playbook
with tasks_from.
Change-Id: I08bd10539d7f08e8759f1c22d66dea18821c9d42
People keep recommending upgrading to 2.14 as a step to 2.15.
It's bazel based- let's add it to the list of builds.
Change-Id: Ic037d91bfc631e87e643dbedd231bb21298a11ee
These render as "help" links in the UI and for most of our users will
just be an attractive nuisance since we don't manage accounts and repos
and such directly in gitea.
Change-Id: Iea4bd262dd6304bc1d423f1bf23dacc4333f506b
Currently if you end up at opendev.org it isn't clear how to start
contributing code. Add a "Get Started" link to the nav bar header to
will send you to the opendev developer docs.
Note we may want to consider updating the developer docs to be a better
landing page or even create a new doc for that, but this is a start.
Change-Id: Iee43e2552c1be2e4cd46f43f050e476f140530ad
For our meetpad service, modify jitsi-meet to open the etherpad
when a user joins.
There is an upstream PR for this, but until it lands or is rejected,
this clones from a temporary github repo with the patch.
Change-Id: Idd33a68a4fe7a90c75c5988bd1fd6136b8b7db08
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
base and builder are currently pinned to 3.7, which makes it hard
to consider upgrading to python-3.8. To help with that, make
python-3.7 and python-3.8 images, but point latest as 3.7 for the
time being. Then add version-specific provides and FROM lines
so that we can start being deliberate and clear about our version
choice.
Change-Id: Ibf1d846d5c4a005547785124567ce2900e272a7a
So that we can run jitsi-meet with local modifications, build our
own container images. This builds the base, prosody, and web images
from the docker-jitsi-meet project. That project has distinct
Dockerfiles for each image, but for simplicity, this change combines
them into a single multi-stage Dockerfile. The minor stylistic
differences between the different sections are a result of that, and
are intentional in order to minimise the delta from the source material.
Again, for simplicity, this change does not publish the base image
since it is not anticipated that we will run this build often. If we do,
we could split this back out.
The upstream images are based on pre-built debian packages hosted by
the jitsi project. Since our goal is to modify the software, we will
need to rebuild the debian packages as well. This adds a new builder
image that is used to build the debian packages initially.
The docker-jitsi-meet project also has Dockerfiles for several more
images, but since the immediate need is only for the "web" image (built
from the "jitsi-meet" project), we only build that image and the "prosody"
image (not strictly necessary, but it is also a product of the "jisti-meet"
repository, so it seems a good practice to build it as well).
Change-Id: Ib3177ebfe2b8732a3522a1fa101fe95586dd1e1b
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
We disable these on our VM images, so might as well make our
container images follow suit. Could make them a smidge smaller.
Also do it in the gerrit-base image.
Change-Id: Iba60cf5c7009d57c4910f9e4464aff9231598ad6
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