subunit logs should not be more than 50MB uncompressed. If they
are you are doing something terribly wrong, and both consuming a
ton of infra resources, as well as local user memory.
Change-Id: I0f93684c0b9055bc95808cfae827e171fa30f6d1
Puppet does not like cron list syntax to be made as a normal string.
Instead you must give puppet cron resources a puppet list that it will
convert to a cron list...
Change-Id: Ia0839be9b7d8ae772065f782adf61f831e75b92e
Job is stable and in order to prevent bringing regressions in upgrade
process, this job should be voting.
Change-Id: Iaac21268ecd2603fafc47dbab3b9a529939c14eb
milestone-proposed was checked out in a detached state, which prevents
git-review from successfully proposing changes to it. It works with
master because master is checked out by default on the initial clone.
This commit makes sure the branch is checked out with proper origin
tracking before proceeding with changes.
Fixes bug #1302490
Change-Id: Iff4f653d2d68fd36bb076ed8ae9fa5b0bb03edda
I hoped with a new project that we could just start out with python 3
from the beginning however there is just too many dependencies that we
can't use then
Change-Id: I24d44976934cd165043b80c779fb4740c53d9dc2
These should be created at a ratio of 5:1 with the tripleo-precise
nodes as we have 5 jobs running on precise for every 1 on f20. When
the jenkins configs were moved to a single global section
Ide8a4026967ad536f6fe21e52694ee746950fb48
min-ready was increased to reflect a new global number for
tripleo-precise nodes but tripleo-f20 images were left at 1.
Change-Id: I0e1eb3dae54d217ea37f1e5a3ff9dedfb1e50c0c
* .../slave_scripts/project-requirements-change.py: When parsing
requirements files, only perform style checks like missing final
newline or duplicate entries on the new/proposed version of a file
and ignore them on the original version of the file in the
repository. This makes it possible to actually correct errors on
imported requirements files, even with the job running this script
already voting on the correcting change. Also annotate this with
more commentary so people have some hope of understanding what the
heck it's doing.
Change-Id: I8ea2800ecc8eb24937e69a573e925b4daf64ff3f
Closes-Bug: #1300843
The gate job for stevedore docs was turned on recently,
but the requirements for building those docs are not allowed
and we are in feature-freeze so we can't add them, yet.
Make the job non-voting so we aren't blocked setting up
library test jobs.
The requirements job for cliff is failing because the master
branch has duplicate requirements and the parser is complaining
before it verifies that an update fixes the problem.
Change-Id: I40b2cf4030df66c851d7d11da4f81f645d110e76
Currently we only have 40 testenvironments and with the sustained
backlog of reviews this can lead to cascade failure (normally the
slight excess gains efficiency by allowing
building/deleting/copying-logs jobs to be doing that while 40 or so
active jobs use testenvs. We'll re-up it once the overload is gone.
Change-Id: Id7332c1d341aa48deae49576839d12b6fdf36b68
this adds a set of tempest-master jobs which provide a tempest
branch override to master. They are lit non voting on tempest,
devstack, and devstack-gate to provide the ability to assess and
fix fundamental issues with this approach.
Change-Id: Id7c472bd726e43513eef13c61947ba09614a06b0
The functional job is only valid from icehouse onwards,
and the api job will only be valid for juno onwards.
Change-Id: I5aa77e91fba97cbe2f00b53831579ae54874bfac
add jobs to tempest master that are non-voting for how things
look like running against a havana cloud.
Change-Id: I18e3f05575181febe3acd7c31f2690e740f6525b
Update the job for running the unit tests of one project with the master
HEAD from oslo.test so that both projects can be specified as parameters.
bp enhance-cross-test-gate-job
Change-Id: Ib13e0ff79f78bcfea6f975a0786ac667d4bb4168
Build a big ugly regex and pass as DEVSTACK_GATE_TEMPEST_REGEX to
devstack-vm-gate.sh causing testr to omit Tempest tests that stress
features not supported by Ironic.
Also updates the job to pull the newer libvirt requirement from
cloud-archive:icehouse. This allows us to drop the workaround for a RAX Xen
issue as well as get some early testing of the libvirt version to be shipped in
14.04.
Change-Id: I4fbbb195997afb662eb6be1c922d8adbacee749e
This lowers the 'unresponsive_hours' variable to .5 in puppetboard
meaning if a node misses its report 3 times it becomes flagged in
the ui.
Change-Id: I5c86fe09ac7647278c63500593c084451b8fc202
We would like to start getting notices of satori changes in our IRC
channel `#openstack-satori`. This change will enable that.
The following commands were issued in #openstack-satori
to allow bot access:
/msg chanserv access #openstack-satori add openstackinfra +AFRfiorstv
/msg chanserv access #openstack-satori add openstackgerrit +AFRfiorstv
Change-Id: Icc225b500cc975ba8a41ac82da3dd15eb50d6a5e
d-g previously had logic around clean log enforcement around
stress tests. However we made an explicit option in change
I50944ad64bec948504a0124ea423a0f96f8a8361
Use that instead.
Change-Id: Ib96b6e6de104a71bc59fd5ea75d2f3897221e178
