Change Id2caf9561b361c1d4950856423282535d067e015 for devstack adds all
repositories in DEVSTACK_PROJECT_FROM_GIT to PROJECTS, so no need to add
repos in jobs to PROJECTS if there are in DEVSTACK_PROJECT_FROM_GIT.
This change went through all of jenkins/jobs and removed PROJECTS where
there is direct 1:1 correspondence. For a few files, especially ironic
and freezer, this was not doable.
Change-Id: I4b51e33b9bc0f1cb7948b69abf104e0b57b9ff52
Add a new job for running osc-placement functional tests (as a tox
env, i.e. tox -e functional) following the approach used by
python-novaclient.
The hook in the osc-placement tree is added in
I8ca156440cb51d03cb8e05185c028573dc6f9b4b
Change-Id: I82295d6682ddc7d7d101b3039d9e1ff678bc1304
Now that liberty is end of life, stable/mitaka is the only
branch that can run on ubuntu trusty nodes and we want to
pair down our list of available jobs a bit. This patch removes
some trusty-based jobs from the nova experimental queue with the
understanding that nova doesn't really need to run these against
stable/mitaka changes, generally either because they don't provide
good coverage or are necessary for the types of fixes that get
backported to stable/mitaka, or just because they probably don't work
on mitaka anyway.
Change-Id: I8a3ee9ed3df1ed08f987b7ae5ea4bed1ed32e758
We want to start testing a feature added to nova which
sends a service user token along with the regular user
token to other services like cinder and neutron during
long-running operations. This relies on a change in
devstack and we only run it on branches after stable/ocata.
Change-Id: Iee859b3a09066dcbc60583210b4107b787f0d79a
Depends-On: I2d7348c4a72af96c0ed2ef6c0ab75d16e9aec8fc
This job is really more than just testing nova with
the placement service (which was new in newton), since
it's also running with cells v2 (also optionial in newton).
The intent of this job is to test the latest features in nova
which for Pike would be things like cinder v3 and
sending service user tokens with regular user tokens (both of
which are available in pike).
We can control the features enabled in the builder based on
the branch the job is running against.
As of this patch, this job is still only running in stable/newton.
Once we start adding some more features for testing in Pike, we
can make this run in master (Pike) also.
Change-Id: Idc3a3c82eaaedb9bd75f9bb4774469853d453899
The post_test_hook.sh used in the placement job for
nova didn't exist until Ocata so the placement job
always fails in stable/newton changes.
This change adds a check for the file before executing
it and also changes the path prefix to use the standard
$BASE variable like many other jobs.
Change-Id: I8bad5aefada01041efef4d37adde980c9358639c
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
Switch master and newton jobs to run on xenial, older branches
test on trusty.
Note that gate-novaclient-dsvm-functional-mitaka runs against
a stable/mitaka environment, just test is done with trusty only.
Change-Id: Ie20339483c46e34bffa6b1a412e8f92a702f0eb3
Runs the Nova post_test_hook which will be used for functional testing
that depends on a real dataset in the db and may be expanded for further
use.
Change-Id: I782e3b62d5d41e18f0341db180dff589830f24c5
Depends-On: I16b2e00eede6af455cb74ca4e6ca951d56fdbcbc
This creates the gate-grenade-dsvm-neutron-nova-next-ubuntu-xenial-nv
job which runs in the experimental queue for nova and grenade.
This is a single-node full grenade upgrade non-voting job which
runs with the latest and greatest optional things for nova, like
cells v2 and the placement-api.
We don't have to worry about stable branches running this because
xenial jobs by design don't run on stable branch changes.
Change-Id: I6d82ec564bdb0e224df49f06a39cd9806529a08c
cell0 is optional in newton but we support it, and in order
to do that we need some test coverage. We want to test both
ways, with and without cell0 (cellsv2), and by default devstack
and grenade run without it.
This change updates two jobs that run in the nova check queue
that will give coverage to running with cells v2 and the cell0
database.
Nova currently has 3 grenade jobs in it's check queue, but only
one of those runs with neutron, and since cellsv2 is the future
and nova-network is deprecated, we add cells v2 to the single-node
neutron grenade job that runs in nova's check queue.
As for the non-grenade job, we add cellsv2 to the placement API
job which runs with neutron and is non-voting in the nova check
queue. Since the placement-api is optional in newton, and cell0
is optional in newton, it seems natural to lump these into the
same job.
This depends on the devstack and grenade changes, respectively,
that use the new NOVA_CONFIGURE_CELLSV2 flag in devstack.
Depends-On: Ic7d0115da51d6ea17ee49071af259a7789c62ab9
Depends-On: I090d5994c3077d86c60457e4c16a03d35e0c409c
Change-Id: Iacb01bca5d946a260f7d1c397d7f14b00a74bb08
This adds a job to nova's experimental queue for testing changes
with the placement-api service running.
It also runs full tempest with neutron (since nova-network is
deprecated) and on an ubuntu xenial node (which will keep it from
running on stable branches also, which is good).
Depends-On: I53dd3e6b41de17387a0e179fc9ac64c143b6a9eb
Part of blueprint generic-resource-pools
Change-Id: Ifae72c0d686faea859b037ac88c15322959b3b33
This adds a non-voting job for running the
python-novaclient functional tests with a neutron
backend, not to be run on stable branches.
Depends-On: Iae49145bb2f09ab1752fdec224c60936c4850c64
Change-Id: Iaf725d9aee02b653d030ffd503292a01c0052972
Related-Bug: #1612410
During current runs setting up the environment is taking long enough
that the tests are given only 24 minutes to run. This is very often
not long enough for the tests to complete. So we're getting failure
unrelated to code changes.
Move the job timeout from 70 minutes to 120 minutes to give us more
time.
Change-Id: I7060287c77b8a86c656464ee3f9cb5135eb3817e
We're about to land some changes that are going to make it important
to get stable/mitaka devstack data with master on the client. This
attempts to setup a job that does that.
Change-Id: I530eb68c97c540d2409248ee02ea28c462ee9b26
Creates a new job that runs nova functional tests in a
identity v3-only devstack, and adds this job to the novaclient
pipeline.
Change-Id: I7c1aa379cd88b7ca5b9af47506f9fdb56978f82f
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
Most jobs installing client libs from pypi now, this means that we don't
need set up the client lib git repos by default in devstack-gate. But
before we can clean up devstack-gate the jobs that do need the clients
need to explicitly state that.
Note that this also setups up ironic and related things because of how
the ironic jobs work they all share a common macro.
Change-Id: I97cc3758d5c97494704406d779a7326420940427
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
Monty Taylor