Previously the swift functional jobs ran a default devstack install.
This results in a cloud that works for running the swift test suite, but
require additional setup time that is unnecessary. Only install keystone
and swift as the other services aren't required in order to save job
runtime.
Depends-On: I1ace341721487e4700de308d3d5b800661210fc0
Change-Id: If169ac7c1b595c69e5800a3c88edd60547b577f0
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
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 newton xenial work. Run swift's functional tests for
>=newton on xenial and continue to run the older branch tests on trusty.
This has been tested by using the devstack-gate reproduce.sh script on
infra xenial instances.
Change-Id: If03dee5e3a1618e289b7b6416267effd5ad68569
Creates a new job that runs swift functional tests in a
identity v3-only devstack, and adds this job to the swift and
swiftclient pipeline.
Change-Id: Ic4cec94823a26da97066f83de29d8838ba718edd
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
The rationale for this change is the same as for merged change
to swift func tests job [1].
The swiftclient functional test job was changed to run
tox -e func as sudo [2]. The job first runs functional tests
against keystone, then repeats the tests against tempauth.
The second part of the job requires SWIFT_TEST_CONFIG_FILE
env var to be set to cause the tests to run against tempauth.
The introduction of sudo in [2] causes this env var to be lost,
so the tests run against keystoneauth again.
[1] change id Ibea153e94e7919b5422a344d365cee3106efb2fe
[2] change id Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe
Change-Id: Ieea3efbd6526edb8038b677a2e2278107acfe211
The swift functional test job was changed to run
tox -e func as sudo [1]. The job first runs functional tests
against keystone, then repeats the tests against tempauth.
The second part of the job requires SWIFT_TEST_CONFIG_FILE
env var to be set to cause the tests to run against tempauth.
The introduction of sudo in [1] causes this env var to be lost,
so the tests run against keystoneauth again.
A tell-tale is that the second run of the functional tests should
output "SKIPPING FUNCTIONAL TESTS SPECIFIC TO AUTH VERSION 3" before
the first line of test results. This has been missing since [1] was
merged.
[1] change id Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe
Change-Id: Ibea153e94e7919b5422a344d365cee3106efb2fe
the swift functional jobs need to run as the stack user if they are
going to build the .tox directory in the appropriate tree.
Change-Id: Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe
This fix allows the swiftclient functional job to use swiftclient from
git, instead of only from pypi, which is needed for testing commits to
the client.
Change-Id: Ib239e55993b6cdc462db7b9854061b7352bbdccd
the swift functional tests should use tox targets when run in the gate
so that their test requirements can be specified in the swift project
itself, instead of being bound to what might be available in the base
image.
Depends-On: I730f1bb530215ba7c30bf32a1c3bbc16edd5c217
Change-Id: Ida1ee74162cb3b0f575364f9e4bf7742ccd9a794
The functional test for python-swiftclient currently fails all the time because
an required package for testing (testrepository) is missing.
swift itself uses nosetest to start functional tests, but python-swiftclient
uses testr and thus requires the package testrepository to be installed.
This patch simply installs all requirements for the tests. I was able to
reproduce this error localy using a fresh virtualenv environment, and this
patch fixed it for me.
Change-Id: I5417f74d324b1915155e321c3a87138069aa35fa
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3