-quick-start steps are modified and fit more to what a reader would do
-quick-start test code is mainly splitted into 2 files, one which is a
setup part as a role, the second one starts with cloning the test
repository, just like all followings tutorial will do
-some elementary steps when manipulating or checking gerrit are being
added as roles
tutorial ssh config: test ssh configuration has been modified to allow
using a known_hosts file for both someone executing localtest and
opendev.org's zuul. A reader executing the tutorial would still have to
accept the fingerprint. To do so, commit-msg hook is fetched manually,
otherwise it would be downloaded by git-review throught scp. Alas,
git-review doesn't allow to pass options to scp to provide a new
known_hosts file.
User's ssh key is used if ~/.ssh/id_rsa.pub is available, otherwise use
a generated one.
- "to_json | from_json | json_query" in test is due to an issue between
ansible and jmespath [1]
[1] https://github.com/ansible-collections/community.general/issues/320
Change-Id: Id5c669537ff5afc7468352139980ebade167d534
Installing docker and pip are pre-reqs and we're using zuul roles
to do them, so they're not really testing explicit quick-start
steps. Move them to pre-run.
Change-Id: I374dac18b9b7e376d924b11f4661355ea7c4d149
We assume pip exists and were getting it from opendev images before.
Add ensure-pip so that pip exists.
Depends-On: https://review.opendev.org/735904
Change-Id: Ifbd32f11f09c518062ffa350f9ebbe597493df67
install-docker allows us to install docker-compose, so why not just use
that instead and test our roles.
Depends-On: https://review.opendev.org/707902
Change-Id: Ie45cbcd6ad05d035e708fed45348e498a35a8eac
With the removal[*] of refs/publish in Gerrit 3.0.0, git-review
1.27.1 or later is needed to avoid attempting a push there and
ultimately failing. The git-review package in Ubuntu 18.04 LTS is
too old (1.26.0), so use latest from PyPI instead.
Adjust the quick-start document to install git-review with pip, and
on Debian/Ubuntu suggest including the python3-pip distro package
since it's split out separate from the interpreter packages.
[*] https://gerrit-review.googlesource.com/c/gerrit/+/192494
Change-Id: I247fb761667a99cf9f25478b49c5a1fe5d11a6cf
The job no longer needs to build duplicate copies of the images,
it can fetch them from the buildset registry instead.
Change-Id: Ibcca12c20d29b9b45a67b65934e5a02087c8cdf8
While pbrx is nice and all, it's quite the divergence from how
the rest of the container ecosystem works. Switch to using
Dockerfile and the python-builder image.
Bind mount ld.so.cache into bwrap context
When using images based on the python:slim base image, python
is installed in /usr/local and the linker needs to know to look
in /usr/local/lib for shared libraries.
Depends-On: https://review.openstack.org/632187
Change-Id: I84f6dd2a8e3222f7807103dcbb61bdadedfdd22d
This allows us to show build history in the web ui.
Also add a local test playbook for the quickstart which basically
does what the zuul-quick-start job does, but expects to run locally
on a workstation (ie, does not install the docker registry and
docker).
Change-Id: Id62dcf69f48399dab3d1259679bf2fc2ce50460e
This test is trying to test a user process on a typical VM/workstation
so make sure that apt behaves in the default manner and installs
recommended packages (such as docker itself).
Change-Id: I62b1367f9d4311deedf16176fa3f97cf0b3a74f1
This playbook performs approximately the same steps documented in
the quick-start tutorial. Use it to verify that things still function.
Note that it does not yet build the images from the current source
(rather, it downloads them from dockerhub) so it is not suitable
as a gate check (it does not use the change under test in zuul).
It does, however, use the sample config files from the change under
test, so can be used to verify changes to those.
Incidentally, this is the first-ever live functional test between
Zuul, Nodepool, and Gerrit.
Change-Id: I5b3dc4b8a8d409787d07b4ad155898f97f1e9eb9
Guillaume Chauvel