These nodesets are currently defined in openstack-zuul-jobs but
should really be here for the convenience of all tenants.
Change-Id: Ie7fa634048304a64a1d86de22f1315e03b9e6e9c
Depends-On: https://review.opendev.org/670384
In Zuul, we're publishing both the sdist and the js-content tarball,
but because of the strict naming rules encoded in the promote job,
they are both renamed to "zuul-master.tar.gz". Instead, let the
js content job specify that it should have a slightly different
name.
Change-Id: I57e6173e3ee058665e908aba786f8966a8d812f4
We need the roles from zuul-jobs for linting our playbooks. This
is copied from project-config. In order to satisfy that, add
zuul-jobs to the required projects so that it'll get cloned and
pushed to the test node.
Change-Id: Ib2e2a6a4b05071199e14570c445dc1a2eda9e9b7
The openstack-zuul-jobs-linters job doesn't exist, since it's
in the openstack-zuul-jobs repo. Just use tox-linters.
Change-Id: I77a3849086dd234bc374305ae4853d2f56e39daa
The design idea for these jobs was that the buildset-registry job
would be used in systems where a dedicated registry job was desired
(e.g., because there are multiple image build jobs). The image-build
job inherits from the buildset-registry job so that if a registry is
not already running, it runs one, but it overrides the playbook so
that it does not pause. In other words, it was meant only to do what
is necessary to build its own image(s), not to serve them to other
jobs.
However, in the (arguably common) case that a repo has a single image
build job as well as jobs which could consume those images, it would
be efficient to have the image build job run the registry, build the
images, then pause for the registry to be used by the consuming jobs.
Rather than ask users to make a new playbook which restores the job
pause, let's have the image build job pause iff it is running a
buildset registry. If there are no child jobs, Zuul will resume
the job immediately, so there won't be any change in behavior. But
if there are child jobs, they will be able to use the registry
running on the image build job.
Change-Id: Iebd47305eeafbfaac0f699aae3e0a7d7a36f85ee
Ansible will try to expand all of these variables if any is used,
even if some of them aren't used. Therefore, make sure that
we have values in the jinja templates for zuul.branch or zuul.tag.
Also, correct the redirect content to avoid a loop.
Change-Id: I426c99b66ff00b709f249cb78bfc6c3d200f73cd
This publishes to pypi in the usual manner, though it does not
GPG sign or upload to a tarballs site (owing to the lack of a
tarballs.opendev.org site at the moment).
Change-Id: Ia9c078841acd741149a8c5eae80393bbfd4aaaa6
This refactors the docs publication/promote jobs so that there
are base versions which can be consumed by tenants who will supply
their own AFS secrets, as well as versions for use in this tenant
(which consume the base versions in exactly the way another tenant
would).
The documentation policies for the tenant are encoded in the secret,
so each tenant can choose the publication locations and scheme once
and allow all projects within that tenant to use these jobs.
Change-Id: I8f201c0351d4d532ddcbcf1f22f9297dece04fff
Obtain and destroy an afs token before attempting to write to AFS.
This also adds a new secret with the keytab for a new opendev
afs service principal.
Change-Id: Ia76f288b894b396effe72ec66eb49237f3f6cea6
This is a new style of docs job which transfers data
via tarballs and can publish branch-tip documentation
in the promote pipeline.
Depends-On: https://review.openstack.org/645384
Change-Id: I6f30f9c7016f54ee66d90c6dc3e6d9c603724b10
Before changing the default nodeset on the base job, do it on
base-test so we can perform preliminary testing of the intended
change.
Change-Id: I8e61bb53d561b5a5159382afd2c9791cae32a17a
The buildset registry job "requires" images, because that's where
they are imported into from the intermediate registry, even if
the buildset registry is run as a standalone job.
The build job inherits from the buildset registry job and therefore
no longer needs an explicit requires line, it inherits it.
Change-Id: I4372f1255411c96d6f65a10368805df785977481
This job inherits from promote-docker-image in zuul-jobs which
contains this playbook already; therefore, this job simply
duplicated the playbook. Remove it.
(You may note this job doesn't add anything to the parent, it
exists only for naming consistency, so that people can just use
the trio of opendev jobs instead of the upstream ones.)
Change-Id: Ib3afc56eadcffe889713dab49f12d836c87c0740
The file is already there, but it wasn't added to the job definition.
The playbook merely pauses the job.
Change-Id: I2ac38fab54da00e6c7671dca0b54b3d9454560a7
This playbook only installed docker, but that's already handled
by the parent job's pre-playbook. This ended up overwriting the
buildset registry configuration.
Change-Id: I8b9fc34e4c1dd045248f6065a31afb975f2f9aae
Add documents to document roles and jobs and a job to test these.
These are not published yet since I don't know where to publish them
currently. Let's add them so that we can ensure that no breakage is
introduced.
Change-Id: I013ab998aba182a29ff4345c975b332406b1a197
Add usual linting job for this repo to have some basic testing.
Also, add the normal .gitignore to blacklist .tox and some other files.
Note this change is not self-testing since the repo is a config-project.
Change-Id: Ie54095f39f9bb4d10d6f809c573ea712f3885af6
James E. Blair