This improves the comments around why we've cleaned up some repo
functionality and also removes the activity button. The activity data
gitea is aware of is not a complete picture and is likely to be
misleading. Avoid misleading people by removing that button.
Change-Id: If7546f95421efdd897f2949e4f89a08d53289ce8
Gitea 1.12.0 brings much improved git repo performance. Specifically it
caches the most recent commits helping the web views render much more
quickly.
This bumps our golang base image to 1.14-buster as gitea has changed
their default golang verison to 1.14. We also add gnupg to the package
install list as the upstream images did this.
In the templates I've tried to comment out rather than remove content
that we don't want exposed. The reason for this is it makes resolving
future template updates simpler.
For v1.12.0 release notes see:
https://github.com/go-gitea/gitea/blob/v1.12.0/CHANGELOG.md
Change-Id: I8fd6587c8962554023d878266055a2bd9d2499f9
When we're building an image that is based off uwsgi-base, the
packages.txt file remains from the previous run which means that it only
install uWSGI again and not the package we're trying to build.
Change-Id: Ic71c47d53566b4ea79e03d19fd355c5c71a62802
Our docker python-base image is a python3 image where python and python3
point to the same version of python which happens to be a 3.x depending
on the specific base image.
One of the things that came up at the PTG is that we'd like to start
identifying where we use python2 in order to port to python3. That is
made a bit more difficult when we use `python` assuming it is `python3`
as we do in our docker images.
Update the images to use `python3` to make this a lot more explicit and
clear that we don't need to port these items.
Change-Id: I54e8f128f0cb8fbbdf54e3748384470262bef3a9
If we match these explicit paths, don't allow the regex matches to
run. Otherwise, we might redirect "/http-bind" to "/" which doesn't
work.
Also, restore the default meet.conf to the upstream; we're not
intending to carry any local changes to the rootfs.
Change-Id: I119d8c223291d79bd5fe0977264dec4bae126280
Many people put hyphens (-) and underscores (_) in their pad names,
and Jitsi-Meet seems to support them in its room names too, so add
them to our rewrite regex.
Change-Id: I819b8d56bf839cf743319e9cd823440c7d910001
Initial testing seems to show that jemalloc is a probable source of our
memory leaks with zuul-scheduler and zuul-web under python3.7 and
python3.8. While this was desireable under python3.5 with zuul-executor
it doesn't seem like we want to enable this universally. For this reason
remove jemalloc from the base image. It can be added into images in
specific places if desireable but isn't a good default.
Change-Id: I671eef4ef27fdde161b52cf0a4187fac10ac8c4e
If the extras includes a '#' inside of it, it means that it is
probably followed up with a comment such as license for that package and
it will fail to install because pip will try to use that literal #.
Change-Id: I31c5ffe3dda3ced4b6a412cc955c73321d4af507
The command is broken (extra ", misses redirection) and duplicates
content from accessbot.sh. Call accessbot.sh directly and use that one
instead.
Change-Id: Ieb530ef27e5995f2848a3c23a6c04a0717716e14
Extract eavedrop into its own service playbook and
puppet manifest. While doing that, stop using jenkinsuser
on eavesdrop in favor of zuul-user.
Add the ability to override the keys for the zuul user.
Remove openstack_project::server, it doesn't do anything.
Containerize and anisblize accessbot. The structure of
how we're doing it in puppet makes it hard to actually
run the puppet in the gate. Run the script in its own
playbook so that we can avoid running it in the gate.
Change-Id: I53cb63ffa4ae50575d4fa37b24323ad13ec1bac3
This lets you build an image to install a package or set of packages
without having to build a fake pbr install.
Change-Id: I6c171881283b89a14a532f31aedb33e223a0ea1f
We produce lists of extras requirements to install, but installing
them takes an extra step. Allow it to be done all at once by accepting
names of extras on the install-from-bindep command line.
Change-Id: Ie75b9a668569c759f78b70617e311ed6f025039a
We need to install the ep_headings plugin. We've got a hack in place
to do it in prod, but it seems like every time we npm install the
plugin in ansible, we need to restart the etherpad container
for $reasons.
It's cleaner to just build an image based on upstream with ep_headings
installed.
Change-Id: Id3b31bbabbbc5f6dcfe56486e48916384292f693
In the 'Join Us' section of the OpenDev home page, OpenDev is
spelt with a lower case 'd'. This commit correctly capitalizes it.
Change-Id: I8d10cdbc89d9e509fa0c688345f5f462ccb539e6
We can link to etherpad.opendev.org now. This is the second to last
mention of openstack.org on opendev.org.
Change-Id: Ie50cf692c5a5cec2f6a6b19d026913d61e0b95e8
Folks looking at the contact section of our Web site may want to
subscribe to the mailing lists we mention there, so provide handy
hyerlinks enabling them to do that. Also add a link to the IRC
channel logs (partly to balance out the bullet list).
Change-Id: Ib3a1ca47b794f84029b3aff43c7a284fc470b7f1
The OpenDev community is moving its discussions off the old
openstack-infra mailing list, so make sure to refer to the correct
new address(es).
Change-Id: I558b60ea0aa3421285d46be449f04198441cf285
We recently added a "Get started" link to Gitea, pointing to the
generic Developer's Guide. Now that the content is split between
"Getting started" and the reference "Developer's Guide", point
to Getting started content instead.
This should be a lot less intimidating for our new users.
Depends-On: https://review.opendev.org/715961
Change-Id: Ifa496bc8de1a6a39d7b52363db3ab49b8175ed9a
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
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
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
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
Upstream stopped running make generate in order to fix their static file
builds [0]. Our static file builds have stopped working with our bump to
1.11.3. Apply the corresponding fix to our dockerfile.
Note that we also use clean-all instead of clean to be sure we clean all
the js and css files first.
[0] 48be1889cd (diff-3254677a7917c6c01f55212f86c57fbf)
Change-Id: I40f0449ae29e185ba7082f2f5a27dc96acf58e31
