The keystone tempest plugin suite doesn't properly tests the
scenario in which ldap is enabled. This change allows the job to run
tempest full suite, including the relevant tests for the scenario.
Change-Id: Idd8291ed53c72c776b9191656d18cc635126cd83
Depends-On: I368ddf34908b906355c422bd1afd6ab9b1a80053
The keystone OSA rolling-upgrade job defines a
builder and job template which duplicates things
done elsewhere. Instead of duplicating job
config, this patch implements the re-use of
other job config.
This also ensures that the primary checkout for
all openstack-ansible scenario jobs is actually
the openstack-ansible repository, instead of
another repository (eg: dragonflow). This ensures
that the correct tests are activated.
Change-Id: I8b0147454ba3ee1ecbd23a6f7c019826690936eb
Adds a CI job to run tempest keystone tests on scenario in which
domain specific drives are enable and there is an ldap domain.
Change-Id: Ieed13cb05db9a4e909217c788ef53819e4aaf901
Depends-On: I8d7aa260b01f675e4ed201ef93bfd66474f4b228
This commit adds a new keystone jenkins jobs the leverages the work
done in openstack-ansible-os_keystone to perform a rolling upgrade
across containers. For what it's worth, the job also runs a
performance script that measures availability of keystone
authenticate and validate API during the upgrade.
Change-Id: If5ac3f00cff61357b59b3339f20b273415202def
We forgot to add the keystone-tempest-plugin project to the PROJECTS
list so the keystone v3 nonvoting jobs are failing with "Invalid
requirement: '/opt/stack/new/keystone-tempest-plugin'".
Change-Id: I727866d4aa8ad3ef8962752dacce3a0e37d1ac01
We need to set the regex in order for tempest to run with tox -eall
instead of tox -esmoke so that the plugin tests are actually included,
as well as to reduce the number of tests to just the plugin-specific
ones.
Change-Id: I438261e9d29c488067522eb7f50cc3c963753836
This patch adds a new nonvoting job for keystone that enables the
recently split out tempest plugin as per the guidelines[1] instead of
running the in-tree plugin. This job can become voting and replace the
main keystone-dsvm-functional job once we know this was set up
correctly.
[1] https://etherpad.openstack.org/p/tempest-separate-plugin
Change-Id: I0f37cadb88966ea572c3aba2265b195b0a6725fe
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
The variable has been renamed in devstack-gate. So update it here.
Depends-On: Ie42a2652da4dcf21103f85d60a4a041b0d436dbd
Change-Id: I176eec52158894c5b24dfb096ef4e4001e1b0ad3
Oops! Missed the append to DEVSTACK_LOCAL_CONFIG in the first cut
the disable_service for swift services is not saved
Change-Id: I688f4aaa5e34916c01214dec1f41ab5feb5006ff
Exactly same as gate-keystone-dsvm-functional-v3-only-ubuntu-xenial-nv,
BUT with swift turned off and python3 turned on in devstack.
Should be non-voting and run only on master for now.
Change-Id: I6d15645480ec042a982e69d640c4a81ee7ddd960
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 service is responsible to install the federation capabilities on
keystone devstack plugin.
Using the non-voting job so we can check it working.
Change-Id: Iab11f04a038435fcf5a4ebaaebadc2ec848c652d
Depends-On: Idfe0eb016370e7776de3525a813d0535cfc75e27
The devstack plugin will live in the Keystone tree and will set
up the environment for our functional tests.
Only adding to the v3 gate for now, since that one is non-voting.
Depends-On: I820ae355ae8f3183fee2b8207e3c17e8bd10dc17
Change-Id: Ibccd2a080a6adc729a83d072de615f95a749efb3
Run the remaining keystone jobs on xenial. The jobs that are voting were
tested using reproduce.sh and worked fine on an infra xenial instance.
In some cases the regexes have been tweaked since xenial jobs by default
only run on >= newton.
Change-Id: Ie42884106f4b9ecb489da1195f9f1cc2fb1f7590
Thanks to oslo.config, keystone now publishes its config file to
http://docs.openstack.org/developer/keystone/sample_config.html after
each update. So, there's no need to run the proposal job for this.
Remove proposal job and script that was used for it.
Change-Id: I7d5623fe91b93af5486670d5f874e065f7cfd8fc
So we can avoid using the jenkins-specific postbuildscript plugin,
move the proposal slave cleanup to a builder. Run it first so that
it always runs. Since we're running it first, we can't use it to
clean up our current workspace, so instead, ask it to clean up all
workspaces.
Change-Id: I54a187d643fb76f10cc11411d546c41348b5592e
Creates a new job that runs keystone functional tests in a
v3-only devstack, and adds this job to the keystone pipeline.
Change-Id: I587ce0b0b4c3f07b34d22360830a603be70937f3
Turn on the keystone tempest plugin tests. From now on, tests that are
only related to the keystone API, will be placed there.
To run only keystone tempest plugin tests, we use::
$ tox -e all-plugin -- keystone
* non-voting so we can see that it works
* master-only
* run only against keystone
Change-Id: I070e1f40ecaa5d23a68c4ac23b542631ea3e2309
Partially-Implements: bp keystone-tempest-plugin-tests
slave-cleanup cleans up more than 100 MB for each job it runs - and it
cleans the same content that we normally clean when starting the job.
so, this will save some space on the proposal slave.
Add the slave-cleanup run to all jobs running on proposal node.
Change-Id: Ide862b0d1d066adbf992de7f542be2d4d20cf9b1
when backported patches are merged the script was proposing
changes to the master branch instead of the stable branch.
refer to https://review.openstack.org/#/c/290180/1 to see
how it proposed a really old change.
Change-Id: I198297c7a1c0044b88709cfedf6628a26e4960bc
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
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 keystone team updates the sample configuration file in it's
own patch, so to not stomp on other patches.
We've had to update the configuration files manually, but we
should create an automated job. Since it's just running
tox -e genconfig and checking diff output.
Change-Id: I0e294b857d9bbf73e7f9c0d0bdee61648fb999bd
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