-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
Reorganizing docs as recommended in:
https://www.divio.com/blog/documentation/
This is simply a reorganization of the existing documents and changes
no content EXCEPT to correct the location of sphinx doc references.
Expect followup changes to change document names (to reflect the new
structure) and to move content from existing guides (e.g., to move the
pipeline/project/job structure definitions out of the "Project Configuration"
reference guide into their own reference documents for easier locatability).
All documents are now located in either the "overview", "tutorials",
"discussions", or "references" subdirectories to reflect the new structure
presented to the user. Code examples and images are moved to "examples" and
"images" root-level directories.
Developer specific documents are located in the "references/developer"
directory.
Change-Id: I538ffd7409941c53bf42fe64b7acbc146023c1e3
The quick start test assumes a compressed job output file but we don't
compress it by default anymore. Handle this new behavior change.
Change-Id: I9db270ae5ceaa98afcd078af0d99460d406295f3
To use the buildset registry we need the docker-compose command to
be executed as the zuul user, otherwise the auth configuration is
not set and the test pulls the images from docker.io.
This change also adds the --digests argument to docker image ls.
Change-Id: I62970cae4851b06ff79cdc953f90772c550000bd
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
We should wait until Zuul has loaded its configuration before
performing the status check. That's slightly complicated right
now, so stabilize the job with a sleep until we work through
the correct solution.
Change-Id: Ia94b14deae16786e5f88507dde637198fceb7707
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
Tell users that the status page exists and point them to it during
the quick-start documentation.
Also, verify that it is served in the quick-start test job.
Change-Id: I8783ac731112af7752e8a7fc34e3337b52c382d9
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