I can't exactly say why, but the horizon postinstall in package.json
runs "tox -e npm" [1]. This then installs from requirements [2].
The requirements gate run a cross-horizon-npm job that ends up calling
this. The short story is that if you modify upper-constraints.txt in
a requirements change, it is not picked up by this job.
Add tox_constraints_file to this job, so we can set the path to the
zuul checked-out version for the test.
[1] e515713084/package.json (L22)
[2] e515713084/tox.ini (L23)
Needed-By: https://review.opendev.org/709389
Change-Id: Ia7dd5af19b42c2ab53dfb70f92e184b0dc215d03
This adds a role which installs bazelisk if it is not already
present. It also adds a test job which exercises the role; the
job will be run on any changes to the new role.
Change-Id: I69b28b58338b46ec3fea696f9d97be4271ed6ae4
On Gentoo this allows multiple packages to compile/install at once.
Change-Id: I23fd629a351b4c6b2acc325611ed47cc04bca404
Signed-off-by: Matthew Thode <mthode@mthode.org>
The install-docker role currently takes care of setting up Docker
however it lacks the ability to install docker-compose at the moment
which is quite useful.
This adds a variable which defaults to false that allows you to use the
role to install docker-compose. It was decided to be put within the
install-docker role because that role already manages the repository
configuration and therefore provide consistency with the repository that
is used to install docker-compose.
Change-Id: Ia6f4ed88b4baf53bd671c7a7b48a1564ff2c866d
This change enables docker user to disable the userland proxy.
Do not merge until the default is set to false (used for testing).
Change-Id: Ib30e409044ccc48b4c19beae36f1bcd453ebef8e
It seems some versions of ruamel do a better job at preserving
comments than others. Create a tox env to regenerate the lists with a
version we know works.
Change-Id: I13503890fd3c18487281e3394b003e9f36cd24f2
When generating index.html files for uploading to Google Cloud
Storage, link directories to their index.html files because
(except in certain circumstances) Google does not automatically
serve index.html files at directory URLs.
Change-Id: Ie854de328057ed080c80df9328163da98014ea36
This allows a deployer to indicate that they prefer the Zuul
dashboard to link to "dir/index.html" rather than just "/dir" when
displaying directory entries in the log browser. This helps with
log storage systems which do not automatically serve index.html
files at directory urls.
Change-Id: I0444798c689667e51d8761a20b661f8a9b90323d
High Availability packages have been added as part of core CentOS
repositories in 8.1.
This patch add this repo and enables it as it provides corosync and
pacemaker based HA solution and some other packages required for it.
Change-Id: Idbddd81f251c1ade97892128e52f9214420bead7
We have to be careful about avoiding outer loop loop_var conflicts in
ansible. Because the zuul-jobs roles are meant to be reconsumed
elsewhere we should not use 'item' loopvars and instead set them to
something a bit more unique.
We use a zj_ prefix to try and be unique to this repo and document this
convention.
Change-Id: I20b9327a914890e9eafcb2b36dc8c23fb472bc8f
If we install our own local version of tox, we should set a fact
with the tox_executable so other tasks can leverage it.
Change-Id: If6895bbb898261e88c0e3083d21210209f79995f
The upload-afs role is actually fairly specialised for uploading docs
with its root-marker scheme. As we're moving more parts of our
infrastructure to publish via AFS I think it's worth making this quite
explicit by renaming the upload-afs role to upload-afs-roots. This
should be transparent as we call the renamed role, and once callers
have been migrated we can use the usual deprecation process.
Add a partner role, upload-afs-synchronize, which is more of a
straight copy with options to synchronize. This will be suitable for
uploading tarball and release artifacts. This is similar in concept
to the promotion job used by zuul [1], but in this case will be
focused on the extant publishing jobs in project-config which don't
currently use the artifact-reporting/promote process.
[1] https://opendev.org/opendev/base-jobs/src/branch/master/playbooks/artifacts/promote.yaml#L39
Change-Id: I493d8829e3fd98e84f1b8f0e776e7ba41abf16c2
Story: #2006598
Task: #38600
The default loop variable 'item' cannot be nested. Because roles like
collect-container-logs may be called from higher level loops that use
'item' we override the loop control var to a name that should be unique.
This should probably be done to all of the other roles in zuul-jobs too.
Change-Id: I2f647596dd40c662aa7447e3d3c8844a77c6b109
Explain the intention of this role and the details of .root-marker,
some of it is copied verbatim from the infra-specs repository design
document.
Change-Id: I6d9124c7eafadc4b53626ff2fef6be6399f61947
Don't try to create change tag if zuul.change is not defined that is the
case for periodic builds.
Change-Id: I5a7e02caf0f502e90e0477daeee868bf06dfbb5c
This change enables using fetch-javascript role along with
the fetch-output role. By default the role still synchronizes
artifacts back to the executor.
Change-Id: I8450ecf91b3387445ebe2436754d1b88f2a77844
This change enables using fetch-subunit-output role along with
the fetch-output role. By default the role still synchronizes
artifacts back to the executor.
Change-Id: I50a50856b96a9112c1b4be82ca04b612fd29d939
