Remove special treatment for mitaka in jobs where the repo has now
the stable/mitaka branch retired.
Change-Id: I1af11cf22c145bb96e93485460cca277287c88ca
Neutron fullstack jobs were running instead of the intended
Neutron FWaaS fullstack jobs after [1] got merged.
This patch corrects the same.
[1]: I98b58355b558fba9a17e75284a42db2813fb20ac
Change-Id: Ia10b9bb4cf4ac747154d2c6d9cb7c301d5bfb5f3
Now that the openstack client fully supports FWaaS v2, add a fullstack
testing job for neutron-fwaas. This will be experimental to start with,
since the change that implements fullstack testing [1] is still under
development.
[1] https://review.openstack.org/394619
Change-Id: I98b58355b558fba9a17e75284a42db2813fb20ac
Liberty is EOL, start cleaning up all of the special things we have in
place for handling libertyisms. Note that this doesn't touch the configs
for deployment projects as they may still attempt to support liberty via
distro packages.
Change-Id: I7faa16c1d6038204a4b42167ed91b73175abe58c
The multinode test definiton for neutron-fwaas omitted proper loading of
the neutron-fwaas plugin.
Change-Id: Ic898203c58ea390f11b53b91e29d18fc4585ab9e
We have now some rather long job-template names, shorten them with
replacing job-suffix with suffix.
Before this change we had 1500 usages of job-suffix and 700 of just
suffix. This change therefore unifies to one setting.
Note that this does not change any job names at all, they are unchanged,
it changes and shortens only the names of job-templates.
Change-Id: I514df039a848d9f6619bca3adc05dfb84a761fc9
These changes are to make the neutron-fwaas multinode jobs work. I also
backport fixes to the grenade job.
Change-Id: Id2f5dddb316bb0304ffe7e32dc9f228735088482
A grenade job is required for neutron stadium compliance, so therefore a
grenade job should be added for neutron-fwaas. Plus, it's just a good
thing to have.
Change-Id: I196973df2260ebbc88f891d6b02830b987e7a9c7
Late discussions on how the neutron-fwaas devstack template should
function resulted in the fwaas v2 case being configured a little
differently. Therefore the neutron-fwaas v2 tempest test needs a minor
adjustment to select FWaaS v2 properly.
Change-Id: Idc91b573eb69e0601576a851963e4bb2914715f0
The neutron-fwaas project has implemented FWaaS v2, while still
maintaining support for FWaaS v1. In order to properly test both of
these, trifurcate the gate-neutron-fwaas-dsvm-tempest job into versions
specific to v1 and v2, as well as a 'legacy' configuration to properly
handle testing from before the v1/v2 split.
Change-Id: I07a4e5a54c0ad862de791b655445e01f805981e4
Depends-On: If35ca26028ddedcf1bc22dd8749cb11c69a1ccbb
Also, enable q-fwaas explicitly as it's going to be dropped in
devstack-gate.
Note: this job is excluded from stable/liberty.
Related-Change: Ic60cd1fa90c19dfac00be583e2ddc5633dbb68a3
Related-Change: Iadcee07e873fcb4f099ebccc2e33780e74438140
Change-Id: I23e39abada43b1ea3c7e95b082c04945305089a9
gate-neutron-fwaas-dsvm-api and gate-neutron-fwaas-dsvm-functional
runs the same tests. This is incorrect. Remove one of them to run
the correct job at neutron-fwaas gate
Change-Id: I4c9d4c90f193073dce2cd91dde7f458f91a830fc
With change Iff5e96bd80b8f165ccc7d6be09b53208613571eb, we do not need
to pass DEVSTACK_GATE_TIMEOUT anymore to devstack-gate, instead the
value from the build-timeout wrapper is passed.
Remove DEVSTACK_GATE_TIMEOUT for jenkins/jobs/[n-z]*.yaml
Increase timeout for all non-grenade jobs by 5 mins since
Iea866e4cc40e149e598f35e010ec855937bdf9ae will use a 10 minute buffer
and the internal timeout should stay the same. The grenade jobs already
have 10 mins of buffer, so no need adjust the timeout.
Adjust timeout for gate-rally-dsvm-cue-{broker},
the removed variable in builder devstack-cue-rally-gate was 100,
so set timeout to 110.
Change-Id: I623fff029fb2e0acdbe2bf93a13af02547062a71
As clarkb suggested on #openstack-infra at 17:46 2015-10-22:
"maybe we should s/branch-designator/job-suffix/g in all those files
as job-suffix makes more sense considering how branch-designator has been
used".
The rename should make it easier for newcomers to understand
these jobs.
This renames branch-designator everywhere in jenkins/jobs/*.
Change-Id: Icb11271b958d92957fb9907ff03c0b898d7b76fc
The intention is to merge this first so that we can test
the api test change [1] by "check experimental".
[1] I8329cb9a14c4348235c3b30208664d649e7245ce
Change-Id: I982933a7fe7b58d4409776c338e319e0f9c2b042
Monty Taylor