Turns out 99 isn't a good prefix.
Also, remove the move argument now that we're merging with the existing
projects.yaml.
Also, stop running zuul unittests on migration script changes. They are
not relevant.
Change-Id: I10ed8cae64c82ed5afd01bb03a74ffc4fd2d87ee
Exercise the infra version of the job, rather than the one that uses the
non-standard docs environment.
Depends-On: I15fce2938222166e75984b75c568fa0fc083a8ee
Change-Id: Ic075a4e1ea434b3770db7d7e62b0738b13f1b333
We need to be able to generate a new v3 config based on our old v2
config. It won't be perfect, but should ultimately be no worse than the
v2.5 auto-generated playbooks.
Change-Id: I9cb676ceff01bbdb845d22774edbaa718323db27
zuul needs to use python-docs-infra because we do docs a little
different then openstack projects.
Change-Id: Iadb38c8ee2e15f1b35233bfc1195d20e01c6d912
Depends-On: Ifc75c7006a79787419cda5d611aa74fbb7ae0b06
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We changed from afs_target to afs_publisher_target.
Change-Id: If0c00ed5754b80fcff7e452cc8103ecfcaed619a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Add a file-based exclusion the zuul-stream tests so that we don't bother
running them unless we're changing the callbacks or the callback tests.
Change-Id: I9066fd93f1794519913d9c9fe0ccc201e4f25baf
This will let the playbooks do multi-node tests so that we can see how
that works in the logs too.
Change-Id: I1ec3496ae3b9da32f4924e09c526a1ebf776ff7b
We need to publish documentation from the post pipeline, this adds
support for that in zuulv3.o.o.
Change-Id: I6c94b2728cb5f8220beb9ba2fa84da4faea68c96
Depends-On: I039ab0e4b67b0bf8416d1c7e0a4d61b45ffb2f15
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Actually run a playbook against a second node with the plugins enabled,
then fetch the output so we can look at it.
Takes advantage of the fact that zuul_console will already be running on
the second node.
Change-Id: I75bcbc46ffbbb49f0689584fbdb1c62ac2e91737
Start publishing branch-tarballs in the post pipeline.
Change-Id: I32144e8f2acc8f67b480ba276af10b84b75753e0
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We need to remove this job from zuul until it has been relocated into
project-config.
Change-Id: I8ef01f14b2bde71c335017f0bbc8532b91f226b6
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Now that zuulv3.o.o is gating on the zuul project, we can start
publishing 'master' tarballs in the post pipeline.
This also removes the tox-tarball job from check, which is no longer
needed for testing.
Change-Id: I854fd50abf76d66a253bd852eafbd75dd42cce24
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
OpenStack Infra is running Zuul v3 on Python3. We're adding things, like
the websockets streaming, that are python3 only - and testing them turns
out to be extra hard even with skipTest because of the syntax changes.
There are no legacy Zuul v3 installations to worry about, and the
Software Factory team has verified that Python3 on CentOS 7 is not a
problem. It's time to pull the plug.
Remove python2 jobs from running in v3. Make the tox defaults python3
for all testenvs and update setup.cfg to indicate that Zuul v3 supports
python3 and not python2.
Also fixed a python3 bug in zuul command line client that shows up
when running zuul --help under python3.
Change-Id: Icaccab9f6edcdba0b87ec0b5f0411d3dc8030b42
Because our playbooks and roles now exist in external repos in
openstack-infra, we can inherit them and start testing again.
Change-Id: I32125a5f1981fc99a0b9202fc530a9ded633a2c2
Depends-On: Ib776cdce10b1f05501c46f6cf359723960f1bc71
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The time has come for us to move our playbooks and roles into
openstack-zuul-jobs and openstack-zuul-roles. This will allow us to
better organize things as we move forward.
Change-Id: I11da723df8823091f25e2a630e80ee4270d99a9b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
While this job shouldn't be in the check pipeline, add it today so we
can test things. We are still missing publishers, but that is
expected since we are missing secrets from zuulv3-dev.o.o.
Change-Id: I12a8a0e156cba1c7e5631da5f05478bb0b8ce957
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
As we start to grow our playbooks, start grouping them by directories.
Change-Id: I487023a7a5e7dccb24843cc4a85f7f9c71c10a83
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This will be a top-level variable used to define the workspace root
for our zuul user.
Change-Id: I4ecd6ead4975691798404f8d9510ed47e20e0c0c
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Here we now support 3 tox jobs; cover, linters and py27.
As you can see by looking at the code, we are not defining any
variables (vars) in .zuul.yaml. This means, we create 3 separate
playbooks (tox-cover.yaml, tox-py27, tox-linters.yaml) which then
contain the variables we need for our tox role.
Change-Id: I42f8855f44da51cb3d23f1825bd3258937543b2f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Copy the logs folder in the JobDir under Apache. This will allow
external users to view the results of the job.
Change-Id: Ib05f6f92f144ed66de986ba863730c8391999c2a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Here we are creating out first in-repo job configuration for zuulv3.
One of the more simpler jobs we can define is the tox -epep8 job.
Change-Id: I4ecacf1b9ca664a98f06f5b998f19410fa7ea11d
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This is overriding the static config that is being defined in the
project-config that is currently being used in testing.
Change-Id: Ic83eb74bb0e34c1231eb8b55b55d55ca5f728bfe
Monty Taylor