Magnum always need to have neutron enabled to work,
so the test with neutron disabled will always fail.
Change-Id: I9d37a052d0beef3b837385324d9f9fa2f1ec9617
This fixes a configuration error:
We do not need both server-release and publish-to-pypi jobs, it's an
either or. Server projects do not release to PyPI and vice versa.
Remove openstack-server-release-jobs from repos that do not need it.
Having the publish-to-pypi template as well as
openstack-server-release-jobs results in duplicates of some of the
jobs running, especially the tarball and announcement email jobs.
Change-Id: Iea5ffd8860b0541094a7cb1506b3f13d312be5a0
Documentation of these projects is not meant to be published on
docs.o.o.
Remove openstack-server-publish template and publisher-site.
Also, remove openstack-server-release template for those projects
that also have publish-to-pypi. These are two alternative ways of
publishing - either to pypi or not. Specifying both is wrong.
Note that these two changes go hand in hand to to removal of job-group
from jenkins/jobs/projects.yaml.
Change-Id: Ie154cd0bad33e15c3ce9560d4c67a4c1f33e6f15
In order to validate the magnum plugin integration,
add more experimental jobs to ensure we have proper coverage
of all tests before moving to check.
Change-Id: Ic3ffc4996eac2d3a7e817ef732f75d0204bd3a80
This job adds a release notes job for searchlight-ui.
Change-Id: I595584ae4c9ffffacf3908fd8cfc223d644441c2
Depends-On: Iedf8c24afa41a7341f32ad2907c758df896c35af
This fixes a configuration error:
We do not need both server-release and publish-to-pypi jobs, it's an
either or. Server projects do not release to PyPI and vice versa.
Remove openstack-server-release-jobs from repos that do not need it.
Having the publish-to-pypi template as well as
openstack-server-release-jobs results in duplicates of some of the
jobs running, especially the tarball and announcement email jobs.
Change-Id: I4a20febd682617becaf9ba6f5660f4931b8d96f1
I am not aware of any efforts to fix the job. The job is more or less
useful in liberty though, where it often times passes. So removing it
for kilo only.
Change-Id: I616d8974cc621dd7d947b1bb79deacc4b326dc8e
The job fails because it attempts to install rally using global
requirements from kilo. Rally does not provide us with a stable/kilo
branch to use, while it also requires some dependencies that are not
present in global requirements in kilo (like python-manilaclient).
I don't know of plans to fix the job, so it's probably better to
deprovision it.
Change-Id: Ie7c74ae2917e0da74355e683c2df48cf6ff42a86
This is a repo for integration tests for all StackLight plugins:
- Elasticsearch-Kibana
- InfluxDB-Grafana
- LMA Collector
- LMA Infrastructure Alerting
Change-Id: Iab22ff0ce1929144d4b0230092341ea18b622c48
We do not need both server-release and publish-to-pypi jobs, it's an
either or. Server projects do not release to PyPI and vice versa.
Having the publish-to-pypi template as well as openstack-server-release-jobs
results in duplicates of some of the jobs running, especially the
tarball and announcement email jobs.
Change-Id: Ic2a82d440577154126218feaaa17cde28ffbf5fa
The translation team only handles official projects - and even
prioritizes there. There's no real translated content up for vmware-nsx
- only filling by translation memory.
Change-Id: If1eb167309e4c5a1de6aa8baed5ff4fc6cfe8b5b
Depends-On: Icb3d33af0e32919bb13c52b3662f481c2c99011c
Now Zaqar supports mongodb and redis as backends. So it would be
nice if the tempest job can support both.
Change-Id: Ie56471c866ff890988d2ced10253051552c73123
The current tempest-dsvm-full-ceph-src jobs aren't using the
ceph devstack plugin, so this adds a template for a new job that
uses the plugin: tempest-dsvm-full-ceph-plugin-src and replaces
the old ceph-src job with it.
Change-Id: I91742ba412d742e9a24681dbc124f00500537315
This reverts commit 4f96b2727c2afd3c3d6b888c21c8d18ba1cb7376.
The correct fix for this is not to stop using the feature.
Change-Id: I4b35a6ca13153257984074b5145a5e691564e0ca
This patch had been proposed before:
https://review.openstack.org/#/c/295969
But had to be reverted because we were consuming external images
from fedorapeople, that caused our tests to timeout. We are now on
the situation where we have our own custom atomic images, to start
adding that on shade as a previous step for adding magnum integration
to shade.
Change-Id: Ifae8e54e78f6f36cf025ac92ba704391b2052769
Inspector tempest plugin was moved to ironic_inspector/test
directory, so we need to exclude inspector_tempest_plugin directory
from regex for matching all tests.
Change-Id: I857a39a72bfebbacd48e9f3d76431367f43d72a7
