layout.yaml - Removed Python3 jobs temporarily until
we set our local tox to run py34 instead of py3.
vitrage.yaml - Fixed hook function to use source
URGENT - Thanks :)
Change-Id: I58994cf77608df5310d6a2b45de195dcc718cfe2
Turn on the keystone tempest plugin tests. From now on, tests that are
only related to the keystone API, will be placed there.
To run only keystone tempest plugin tests, we use::
$ tox -e all-plugin -- keystone
* non-voting so we can see that it works
* master-only
* run only against keystone
Change-Id: I070e1f40ecaa5d23a68c4ac23b542631ea3e2309
Partially-Implements: bp keystone-tempest-plugin-tests
As the work to implement CentOS7 support in OpenStack-Ansible is
low priority work which is being done over several cycles, the
jobs to implement this are being moved to the experimental queue.
This will reduce the OpenStack-Infra resources wasted and only
implement the jobs on-demand.
Change-Id: I52e044a6d47691cca52e6c76f6b6268c01003434
We would like to start implementing functional testing on puppet-ovn and
this patch is a first step for having those tests, with Beaker.
Once we have basic beaker tests, we'll continue testing with
puppet-openstack-integration later.
Also add reno jobs to manage release notes.
Change-Id: Ib70a4cc724d4a17d0c1eab952bd872ac46f76b0a
This job adds the CI jobs for Trove Dashboard. The change 3e0ad3e
already added the release notes jobs to the Trove Dashboard project's
tox.ini etc.,
I'd followowed the documentation at [1] which didn't mention that you
had to add the doc-publisher-site. I have therefure also submitted [2]
to update the documentation and pointed the example to this review as
it contains the three steps that are required to completely execute
this process.
[1] http://docs.openstack.org/project-team-guide/release-management.html#how-to-add-new-release-notes
[2] https://review.openstack.org/#/c/307161/
Change-Id: I6adb4934e82b934e1c8aa992c42e2377ef7a9732
Add releasenotes & beakers jobs to puppet-ec2api, so we can start
managing release notes and functional testing with beaker.
Change-Id: Ib200d0598d2f77f31451a46a237e2960608f5709
The Horizon Django 1.9 tests were recently made voting[1], but were not
disabled for stable/mitaka, causing the gate to be blocked.
1. https://review.openstack.org/#/c/305940/
Change-Id: I2e4145838e75d89492bac72ffd737f236171f0b0
Currently ofagent jobs don't work for stable branch by the patch[1]
was merged. This change fixes its bug.
[1] https://review.openstack.org/#/c/303121/
Change-Id: I7233e526bfc814980bcd4619806478c646407719
* Make gate-cue-python34 check job voting
* Use python3-jobs template to also add gate-cue-python34 as a gate
job
gate-cue-python34 was fixed by the change
I45e23b71218f5ff936b0fd1bd628f29210f984bb.
Change-Id: I4fb16a74d2bf560e08afdfa412b1ccd74fea6da3
gate-tempest-dsvm-ironic-pxe_ssh-dib is reliably failing with no clear
cause (see reference bug). While this is being investigated, make the
job non-voting to unblock the dib gate.
Change-Id: I025b1fd07f22a1de247304e5b2039253f0285476
Partial-Bug: #1571492
1. Added vitrage.yaml - needed for setting up environment vars and
run tempests tests.
2. Added Jenkins template jobs publish to pypi and python3, for the following projects:
- vitrage
- python-vitrageclient
- vitrage-dashboard
under projects.yaml and layout.yaml
3. Added an experimental template job for running tempest tests under layout.yaml
Change-Id: Ib882a4dd60d1b26caf861d74773b8e7f9e8aa2dd
https://review.openstack.org/#/c/302547 added the
uc-recognition repo. This commit adds the relevant
gerrit and zuul changes to make it work.
Change-Id: I9378b93ecdc917f8115e8b10921492d620d37bec
This change proposes to move two of the Trove scenario tests that were
being run in experimental to the check. These tests pass, but not
reliably. The failures are now largely related to timeouts and these
are being addressed in[1], other false-negatives which were seen
earlier have been now addressed.
Since these are now in the check (and no longer experimental) the
branches where they will run has been restricted to master, and moving
forward, newton, ocata, etc., The stability of the tests in mitaka is
not sufficient to make it worthwhile running there, and the tests are
not complete in earlier releases.
[1] https://bugs.launchpad.net/trove/+bug/1571092
Change-Id: I9135544e5c97ad9f129945006cc5b16a70d617e4
Similarly to what was done in [1], this is about scenario tests.
The job did not take off in Mitaka, so add the release to the list of skipped branches.
Drop the s suffix for consistency.
[1] If5f7ea82c45494953452f728fabb7403d0b6e14e
Change-Id: I77827d2e6e07fbfb39727d823628094d730fcdd8
