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. For changes against
branches >= newton run jobs on Xenial. Older branches continue to run on
trusty.
Change-Id: Idfc480c1a7732543c4aeb167146e0e670e6f509d
rally project previously needed to copy something to devstack
during installation. right now 'rally' is a devstack plugin
and it doesn't need it.
Change-Id: If1d90f5274c94bfba90889f457d65a525ff2aae4
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>
Since ec2-api`s rally job uses own flavor 'm1.nano' is not
needed.
And rally script creates m1.nano by self and fails if tempest
created it before.
Change-Id: I3c021956ddc47a6c4cc9bb8c3f5b669c51e3b0e1
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/[e-m]*.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.
Change-Id: Ied54d602d0cd1b994129f979ec25290e54980426
pass environment variable to devstack plugin in a right way
remove TEMPEST=1 definition - it is not needed becuase this
experimental job runs own functional tests
Change-Id: I85f6fa23fc0a819260300d75dc2307c06e44e6c8
removing job that runs tempest tests against ec2 api.
because there are no tests in tempest for ec2/s3 now...
Change-Id: Iebc8c805b37db6a82614d00e904a34d2f369d844
Between the Icehouse and Juno releases, OpenStack changed its
supported Ubuntu LTS platform from Precise to Trusty. In support of
continuing testing stable/icehouse and prior branches on Precise
while starting to test newer branches on Trusty, a branch-based
decision tree was introduced into our Zuul configuration by way of
complex parameter functions with an ever growing list of regular
expression matches on job names.
Now that Icehouse is EOL (in fact, Juno is too) this simply adds
unnecessary complexity and an attractive nuisance for cargo-cult
copying into new job and job-template definitions which don't even
need it. In preparation to remove the associated parameter
functions, get rid of multiple labels in all jobs and set them to
whatever label Zuul would ultimately select.
This change touches a vast number, possibly a majority, of our jobs
and so manual jenkins-jobs updates on all Jenkins masters will be
needed after this merges, before it's safe to approve the
corresponding Zuul configuration cleanup.
Change-Id: Ic952ee02da2c77fe2ace81c4e2fa87531be6119c
because ec2-api functional tests are very aggressive then
four workers can exceed quotas. but two workers should work well
as we saw in the past.
Change-Id: I1b1b735c5f3eb5af308d7de55e4de89ed0161a13
Since tempest team implemented plugins and we reworked our ec2api
functional tests to suite tempest`s technology then we can
rework our main gating jobs to use modern way to run functional tests.
But we left old code for stable/kilo branch.
Change-Id: Ib565e1b1095cdafdbe908fe1b1406f57d834fbaa
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
added rally plugin to list of plugins for ec2api job
with rally. since rally needs to be as plugin in job configuration.
Change-Id: I6103f9b40786d65ca8de380137ee02e71fe5b98e
Additional project should be added to PROJECTS as I understood.
It needs for clone the project to /opt/stack if this project enabled
for devstack.
Also, as Ian Wienand asked about regrouping definitions in patchset #1.
So I regrouped definitions in another job too to be similar.
Change-Id: If7e891cdedb3342a326253bca7391a0495959f69
Recently (by Idd5524ed0b602408be5a53830981a8ab974b390c) VPNaaS was
removed from default service set.
But since ec2api supports VPN related features, it needs VPNaaS in
the gating job for functional testing.
This patch adds VPNaaS to jobs which run vpn related tests.
Change-Id: Ia1f5f8747ab82f02c3fae9536c6a91ce84af7833
My mistake. I've copied job definition from job template where
brackets are twin. But new job is not template and definition
requieres only one pair.
Change-Id: Ib08cda75b492270ae2cafa0f15cbd86fe7e60296
Add one more checking job for running all functional tests
against ec2-api project. Add this job to experimental pipeline.
Previosly functional checking jobs run only quick tests (up to 30-40 seconds).
But now we wrote some long scenario tests (up to 300-400 seconds each)
and we need to run it periodically for 'integration' testing.
Change-Id: Ibdad27cb3743518c1194e00d5e9181cde0e65f5c
1. Do not run tempest with own functional tests jobs.
It takes more time and don't allow to run fake-virt-rally job.
because scenarios' tests can't be passed with fake virt.
This fix sets to DEVSTACK_GATE_TEMPEST_NOTESTS 1,
in conjunction with DEVSTACK_GATE_TEMPEST. It will allow Tempest to be
installed and configured, but the tests will be skipped
2. Temporary switch off voting for tempest against ec2-api backend.
Current tempest has two incompatible tests -
diassociate_not_associated_address
and run instance by image/kernel/ramdisk(This feature
is broken in current nova code as I understood)
Change-Id: I7bad03ffb5e4fa3bc13457dc18bde7040458aa78
1. Enable tempest for rally gate. Only tempest preparation code has needed falvors creation -
flavors without disk(m1.nano for example). We need flavor without disk because only this can be
run with fakevirt driver due to bug https://bugs.launchpad.net/nova/+bug/1433994
2. Add calling hook script before running rally to setup specific things of third-party project.
For example - botocore. This library is absent in global requirements and can not be add to ec2-api
project. And global requirements is frozen now for adding new.
Change-Id: I9993c97ecb6900efefc8ae73107d8a06a9e6dcf6
Zuul expects the job to run on "devstack" workers because of the
"dsvm" in the job name (there's a zuul parameter function which
matches those up for convenience), but in this job definition I
have specified "bare" workers so that's all Jenkins registered for
it. As a result, zuul doesn't see any of the worker types it expects
registering that job name. I must correct the "node" parameter for
the gate-rally-dsvm-ec2-api-fakevirt job definition in
openstack-infra/project-config:jenkins/jobs/ec2-api.yaml then it
should work.
Change-Id: If5740498cb059e8219b2b9db4a4c565d2bc1b04e
In previous review
https://review.openstack.org/#/c/159138/
I tried to use existing rally job. But I skipped fact that in this job
ec2-api wouldn't loaded. Now I was trying to think up how this existing
job can be adapted to load ec2-api plugin. And simple way to do it -
is to create another job-template with needed shell script and needed params.
Change-Id: I3a95b298a70795601ef4002fc413e91960af0f2b
I made a typo in previous review with unbalanced parenthesis
https://review.openstack.org/#/c/154640/
Here is a fix with simplified regex
Change-Id: I918d53f5d911e29c08ebba29385962364dcbfe5f
Since most of api tests committed and worked -
https://review.openstack.org/#/c/154604/
I suggest to make ec2 gating jobs as 'voting'
and reduce tests scope of simple tempest job.
Change-Id: I933ee62ee58431a277c719fea9ef2732b4a04582
adding jobs that deploy devstack with neutron or without
next these jobs calls post script that runs functional tests
from EC2 project against deployed cloud.
Related change in EC2API project is here -
https://review.openstack.org/#/c/153827/
Change-Id: I95c2500f0a087c0a70d80322f40d3b85b266d1ad
This creates a non voting check job for ec2api changes that includes
setting up a devstack environment using an external devstack plugin in
a zuul compatible way. This is also a good reference for other teams
that would like test jobs which include devstack external plugins.
Change-Id: I8e31fd4f771e498efd5d8671acee0a3c3c8a184e
Monty Taylor