Change I939d48f78bebd0c6d474f49adb8dd077dff4cc7c only added layout.yaml
and now the layout test fails with:
FAILURE: Job propose-shade-update-constraints not defined
FAILURE: Job shade-announce-release not defined
FAILURE: Job shade-pypi-both-upload not defined
FAILURE: Job shade-tarball not defined
Add the job definitions as well
Change-Id: Ic278752d2b1ce8fc68ba68b08e30e1f395e214d1
This reverts commit bf25cc9e7b.
The pin of pip/setuptools to such a low version is now causing the
gate jobs to fail to install packages, since it doesn't understand new
environment markers we use. This probably opens Pandora's box of
issues that we never quite fixed?
Change-Id: Ie3f967d27b03a9594d54e8dd413f61daa65a73f3
Now that whereto is officially managed by the documentation team,
publish its documentation to docs.o.o. This patch attempts to update the
zuul v2 and v3 configurations together, in case the migration is
postponed or rolled back again.
Change-Id: I1e988cfb69abc73fa8efc2448e25851844954815
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
These jobs consistently timeout and we're working to move them out of
upstream to a 3rd party configuration. For now let's switch them to
non-voting so we can stop blocking the ocata patches.
Change-Id: Ibe89019a5b788fb9fcea1b721cc8e25a54f8ea8a
After turning off admin actions via keystone v2, this job lost it's
importance and doesn't check anything useful. It should be complitely
reworked to setup the correct version of OpenStack release (Pike or
Ocata) where keystone v2 exists.
Since it is redundant as for now, I see no reason to try fixing it while
process of moving to zuul v3. Let's make our gates green as a first step
and then returning to the keystone v2 job.
Change-Id: I2e7f6196f42a7e241b261ba1ac7ade84ef8c210a
After setting the UPPER_CONSTRAINTS_FILE, gates started failing
because of side effects, as this var was being taken as part of
the image build. Unset it after requirements have been installed
and before actually running the tests.
Change-Id: I650cf83e2828ce373b8c9e8b3c0cc1c9722b949a
We need to run centos lvm jobs in manila because of
an ubuntu xenial bug and get no additional coverage
by continuing to run the xenial lvm jobs so remove
these as long as we are running the corresponding
centos jobs.
Change-Id: Ida15807d32305aa0c6216007616edbdb3af2e6cb
This patch removes the neutron-lbaas-dashboard and octavia-dashboard
integration jobs as the Horizon team is no longer recommending them.
They were always non-voting jobs in the Octavia projects.
Change-Id: Ifb60ff6ebfa8d88771df35b29406ae8c4e971a83
To compensate for "slow nodes" which cause timeouts on Manila
DSVM jobs on semi-rare occasions, increase the timeouts to
avoid the need to recheck.
Change-Id: I880b9e9cecb05cf32c23ccf3bf70e31d1bcf1827
Since branches <= mitaka are mainly retired:
Remove kolla, mox3 python34 jobs, this is not run.
Remove unused job definitions.
Change-Id: Ie60de78ea85ba9827e1c18775c54031de16405c3
Remove ACLs for stable/mitaka since that branch is retired.
Remove notifications for stable/mitaka from gerritbot.
Remove now unused job definition.
Remove liberty and mitaka in names for the proposal regex since we have
no such jobs anymore.
Change-Id: I45a666b2bc5c8c4e344f3fe0b582c53459742975
We are running into errors when attempting to uninstal hiera on trusty
jobs because the hiera package does not exist. We no longer install
puppet as part of our image build process so we shouldn't need to
uninstall puppet, hiera, and facter at all. Simply drop the the removals
to address this as there is nothing to remove any longer.
Change-Id: I1ce79f3f7dd164e0635a4ae45210194f50ab8ad9
The v3 migration script can handle these just fine - but if we go ahead
and remove them the output can be predominantely shell rather than
script.
Change-Id: I440851a0149e1cc7f8c5c6e8a4e3e0b94088ee82
Remove old trusty jobs from repos that have now retired branches where
the jobs were only run on the retired (<= mitaka) branches.
Change-Id: Ia7a373f486de4fde971436e1a91a37440d79694a
Remove trusty pbr jobs, we have no regex that runs these on master
and pbr has no older branches, so remove these unused jobs.
Change-Id: Ie146ba6cc78bc1050eb8f75792955d9d883e4df7
The keystone tempest plugin suite doesn't properly tests the
scenario in which ldap is enabled. This change allows the job to run
tempest full suite, including the relevant tests for the scenario.
Change-Id: Idd8291ed53c72c776b9191656d18cc635126cd83
Depends-On: I368ddf34908b906355c422bd1afd6ab9b1a80053