We believe the Kolla build will take between 1 and 3 hours. We
are not certain exactly how long it will take, so we plan to
start with 90 minutes and later tune the timer to match our
average run-times + 20%.
Note our gate functional job builds about 40 docker images which
takes quite awhile.
Change-Id: Ifd052464cacbe4ce4d0584277aa729ab151d48fe
Otherwise, the script will fail.
Also add for tox invocation until potential group issue is sorted out
(group membership applied to current running shell).
Change-Id: Ic84d5435761deae0d28909c813cb1d87540fbb21
The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.
Change-Id: I279ebb9526ce6c5010de94d631dfe75a2d32dab8
The setup_docker script downloads and starts the Docker binary while
the tox run performs the actual test of verifying all the Dockerfiles
in the project successfully builds or fails as expected.
Change-Id: I4d05c32a2faa30f0b15487dfd605089f61baf985
This adds the akanda sub-projects to the 'akanda' group, hopefully
enabling patches to these projects to generate updates to LP bugs
on the akanda project.
Change-Id: I246a6cbed1247c4f5f1dcf24d03df9bc03a7e2c8
This is a continuation of I51a86699a39e6f8fdac91ad91f5933246681ae15
which missed moving storyboard documentation.
Change-Id: Ica2f02111aa1c891461a7aca4e86cea71e583530
With commit 8db41f04, "tox -epy34" is now successful in Neutron. Make sure it
stays that way by enabling a voting gate on the master branch.
Change-Id: I1e11c922d79fde4505904f83d477e23927504555
This job is broken. A patch merged into neutron which breaks this job
because this job isn't actually using the neutron patch it's testing
against:
https://review.openstack.org/#q,8db41f04d54526104920f3a160203ecf7ef453b0,n,z
The revert of that patch won't merge because the lbaas-dsvm-api job is
installing neutron master.
https://review.openstack.org/#/c/182413/1
This job should be non-voting until it's fixed to properly test the
right neutron patch(es) instead of neutron master.
Change-Id: Ieca799e069696b460aef8caebda84428643ee259
Magnum is ready for requirements check job to be enabled
with the following 2 reviews.
Depends-On: Ic64996120a3a108b9b6d3c8daa313ea654fedba4
Depends-On: I15310f66ecdcd1fb0496e41e5311cebbba3ba706
Change-Id: Ieb8c5cfa8099b468e8868e3b65cbabf19a002559
Some packages may depend on python-setuptools, which is not
installed and cannot be reinstalled on CentOS 6.x once yum has
erased them, so use --skip-broken to avoid aborting. Also on this
platform --downloadonly causes yum to return nonzero even when it
succeeds, so ignore its exit code.
Change-Id: Iaada39ae81e1e47fe9d0bedba80fd19e4e0e6f38
Since the kilo release we need to verify that tempest and devstack-gate
master works with a stable/kilo cloud for incoming commits. This commit
adds the missing stable/kilo compat jobs to check this.
Change-Id: I3b1277aac985f7b072f26b8c4a3e426c22325312
This adds a test job to run glance_store functional tests with the
filesystem driver. After this is up and running, jobs will be added for
each driver we want to functionally test as they become ready.
Change-Id: Ie4d06a6e2713f8d5b12582b2963271f10970672e
Create functional test job for python-muranoclient, set as non-voting until
its working. The muranoclient functional tests are being extracted from the
main murano tempest-based tests.
Change-Id: I525a53222837c42790268e00d4408abaa99a2efb
Create functional test job for python-heatclient, set as non-voting
until its working. The heatclient functional tests will come from the tempest
cli tests.
Change-Id: Ib6338cdcce3e14ca9191fdc0d1f05e3d2d814125