Remove special treatment for mitaka in jobs where the repo has now
the stable/mitaka branch retired.
Change-Id: I1af11cf22c145bb96e93485460cca277287c88ca
Add gate_hook and post_test_hook for the tempest job.
The former will be used to fix the job. [1]
(No need for Depends-On as it's an experimental job.)
[1] I81e712503a20623bf43bd61c39f79efc306f8e9a
Partial-Bug: #1659691
Change-Id: I1d7d3bdd396b891bcbfe2ef7e40ad9351a13981b
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
This is part of the Trusty to Xenial transition. Will run jobs for
changes against branches >= newton on Xenial. Older branches continue to
run jobs on Trusty.
Change-Id: I93c6b3b332d4764f99367d894e395e738c4dd332
Some issue was found when running the testing of patch
https://review.openstack.org/#/c/337011 online, fix it in this patch.
Related-bug: #1598652
Change-Id: If06ef1adbcefca37cba39a774a57b6f6f1c3d2e1
Depends-On: I38bc7087fe3cb94cfd532877b2a42441c3733620
VPNaaS API CI test is not enabled since the current api test code has some
issues, however our team has fixed it in this patch:
https://review.openstack.org/#/c/335838/, and also vpnaas project need this
API tests, so here create a new API CI job to enable vpnaas api CI tests.
Related-bug: #1598652
Change-Id: I38bc7087fe3cb94cfd532877b2a42441c3733620
This is related to zuulv25, we make sure console-log is the last
publisher to ensure zuul-launcher logs are also uploaded.
Change-Id: I1616b97fad2b97fb9e977ec14543aab4bc673b58
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Set up a job for Tempest Integration of neutron-vpnaas API tests
This needs to be merged so [1] can be tested
[1]: https://review.openstack.org/#/c/279787/
Change-Id: Id8ef765e1cac1f48a5cb156cc81e5500cb9097fb
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
This will change the existing functional test jobs to use a common job
template. To do this the following steps were taken:
- Make the jobs non-voting, so they don't break the gate. This means
that reviewers need to check the non-voting results, prior to +A.
- Removed experimental functional jobs that were previously created,
in neutron-vpnaas repos. These jobs were going to replace the existing
ones (but do the same thing). Aborting that approach.
- Remove the experimental API job. A separate commit will add it back
in, and use the new common template, as part of work to getting the
API job working.
Partial-Bug: #1495584
Change-Id: I015bb7727676a68b1dfc3f04d10a80a308b00435
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
1. Add new experimental jobs to run neutron-vpnaas functional
(openswan/strongswan) and api tests with one job template
2. once this new job template verified and tested, remove old functional
jobs and templates
Note: This idea is chosen based on the community reviews so it should not
affect vpn jobs in vpnaas repo and leaving them untouched
Change-Id: Id4614ea1103a9ecc9b069f0b9cd47c0e385f9eba
The StrongSwan driver has been proposed as the new 'reference'
implementation for VPNaaS, eventually replacing the current OpenSwan
driver.
The StrongSwan driver requires that StrongSwan is installed, and that
AppArmor is disabled for the charon and stroke processes. To do this,
a separate DevStack based functional job will be created.
To support both jobs, and to allow sharing of test cases that may
apply to both driver implementations, the plan is to create the
following directory structure (and corresponding test filtering):
tests/functional/ - Shared test cases/modules
tests/functional/strongswan/ - StrongSwan specific tests
tests/functional/openswan/ - OpenSwan specific tests
Note: As StrongSwan test modules are developed, they will need to
be located in tests/functional/strongswan/. Likewise, the existing
placeholder module for the OpenSwan driver (test cases are empty
currently) will be moved into the tests/functional/openswan area.
As a result, this change will not affect any existing functional
tests.
For this functional job, a different argument will be passed into
the hook scripts to indicate the tests will use StrongSwan. The
gate hook will set the environment variable IPSEC_PACKAGE=strongswan
and DevStack (modified under review 158741) will install StrongSwan
and disable AppArmor for charon/stroke.
Depends-On: fbde695ac2bef255703dc131beeede769d9e005a
Change-Id: Ie0a45fe450ccded61b66a96cd95fac3878d00cfb
Partial-Bug: 1424757
Generally this area of the repo is organized by project, so rename
the *-functional.yaml files to avoid the suggestion that each job
needs its own file. Instead, name them for their projects to suggest
that you can look in each project file to see the jobs that apply
specifically to that project.
Change-Id: I31e95a405c03c207e26f9a63403e1b7205595b7f