Based on the native 'grenade' job.
Also, remove the now-unneeded scenario-py3 job
(probably a leftover).
Story: 2001686
Task: 24518
Depends-On: https://review.opendev.org/548936
Change-Id: I7efddc3c9bbf3ea9c635d6cbe5835e46de017ec3
- set the starting point as train (to be adapted in the
backports of this patch);
- heat tests should have been disabled already here;
they are really flaky, they takes more time and they should be
tested by heat.
Change-Id: I5571ac5e578f98465737373598b358aa7dab93e0
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ic57069fd0acc405347e263a082ea8ba9915e9d41
So far grenade has been testing a queens->rocky upgrade.
Implement the grenade code required to upgrade to the current
master. The plugin code installs the split plugins, which
need to be listed in the PROJECTS variable in order to be cloned.
Also, don't deploy sahara-all even when deploying rocky
(it was already deprecated back then).
Finally, deploying sahara-api using wsgi has been the default
for a while and for sure when the upgrade starts from rocky
there is no need to disable it.
The grenade test should be stable enough again, so re-enable it
in both the check and the gate queue.
Change-Id: I000aae6c093c32ab1c3505448e2b9ec52b0529a2
Run also: the API v2 scenario and tempest tests on both the check
and the gate queue.
Remove the list of plugins from required-project, as it was added
to the definition of the job in sahara-tests.git.
Finally, make sure that the base buildimages job depend on the
sahara repository and that it uses the sahara source directory
as working directory.
Change-Id: I97a302e253516cdd827c522178fca5fb5590f00c
While it would have been better to directly use a native Zuul v3 job,
the work towards a common grenade job seems to be stalled.
Import the job locally and fix some issues:
- make sure that the heat_tempest_plugin is loaded correctly,
so that the heat upgrade tests work;
- bump the starting point from stable/ocata (!) to stable/queens;
it will be changed to stable/rocky when grenade supports it;
will require additional fixes due to the standalone->uwsgi change.
- import lib/apache so that wsgi deployment works.
Story: 2001686
Task: 24517
Change-Id: Ia8de2b8286287355e8e9d3f702027aa282ed8282
It defines buildimages/CLI jobs, and reuses the global pylint job
and few jobs from sahara-tests (scenario, tempest), mimicking
the existing definitions of the legacy jobs.
Still missing: grenade (there is no common grenade job yet at this
point).
Change-Id: Ibb57e216410afeef4d55d8ba2576aaacfa2f8c1a