summaryrefslogtreecommitdiff
path: root/.zuul.yaml
Commit message (Collapse)AuthorAgeFilesLines
...
* gate: Add victoria rolling upgrade jobTim Burke2020-11-091-0/+7
| | | | Change-Id: I6ca407b86658191b2db1e806d284cdd6348c86e1
* Revert "Make rolling-upgrade job non-voting"Tim Burke2020-09-191-2/+0
| | | | | | This reverts commit 63e6c91ab86f3a832d7af9dc081ee90b73d8fa04. Change-Id: I1af54679c48474d3aa375c5d1192871e9bb16c7d
* Run swift-tox-func-encryption-py37 job in the gateTim Burke2020-09-171-1/+1
| | | | | | | | This used to be the name of the py2 job, but now even that's gone; I'm not sure how Zuul let us get away with this. Change-Id: I1a2f22d592fc7245e40c645000026e4ba1fca528 Related-Change: Ia9ae0fc226dfc9b40157faebac100c10a9180c62
* [goal] Migrate testing to ubuntu focalGhanshyam Mann2020-08-171-1/+1
| | | | | | | | | | | | | | As per victoria cycle testing runtime and community goal[1] we need to migrate upstream CI/CD to Ubuntu Focal(20.04). Moving py38 job to focal. Story: #2007865 Task: #40221 [1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.h> Change-Id: I2a1ce0bda37a4764f7e56a9c15a283eefa46e17b
* Bump up probe test timeoutTim Burke2020-06-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | There's been a roughly 5x increase in timeouts in the last three months, which was itself about a 10x increase from the three months prior. Let's get timeouts to be the exception, not the norm. FWIW, some stats over the past two and a half years: Quarter | Median | Timeouts | Pass Time | --------+-----------+--------- 2018Q1 | 19.0m | 2 2018Q2 | 24.5m | 19 2018Q3 | 26.8m | 3 2018Q4 | 29.0m | 2 2019Q1 | 31.0m | 0 2019Q2 | 31.7m | 4 2019Q3 | 32.7m | 1 2019Q4 | 33.7m | 2 2020Q1 | 46.4m | 25 2020Q2 | 47.5m | 134 Change-Id: Iab60b952dfd1060f1166e5a07c9298c75e6831f1
* Merge "dsvm: Use devstack's s3api "service""Zuul2020-06-071-0/+1
|\
| * dsvm: Use devstack's s3api "service"Tim Burke2020-05-271-0/+1
| | | | | | | | | | | | | | | | ...instead of hacking up the pipeline ourselves. Depends-On: https://review.opendev.org/731003 Depends-On: https://review.opendev.org/731065 Change-Id: Iea8a42ef54e1a2fd9c1d6132c840a20015cc5d7e
* | tests: Bump up timeout for unit and in-process func testsTim Burke2020-06-051-1/+1
| | | | | | | | | | | | | | We've been seeing more TIMEOUT failures lately where the jobs still seem to be making steady (if slow) progress. Change-Id: I19c1f48bace551c78ad0c6c8b6ccad75e44e8904
* | Enable s3api and staticweb tests across all func testsThiago da Silva2020-06-011-72/+0
| | | | | | | | | | | | | | This patch removed the separate s3api, staticweb functional tests gate jobs and added them across all other functional test jobs. Change-Id: Ie1c606132a054defc2b3cc14a66031090e7b8449
* | Remove swift-dsvm-functional-py3 jobTim Burke2020-05-271-28/+0
| | | | | | | | | | | | | | | | Following https://github.com/openstack/devstack/commit/6b6bdc711, the swift-dsvm-functional job has been running everything under Python 3 anyway. Change-Id: Ie285f513e1ed71dbaf4e12fe747ea6087664f843
* | Skip tests when only changing README.rst, CONTRIBUTING.rst, etc.Tim Burke2020-05-261-26/+26
| | | | | | | | Change-Id: Ib78398111ee3d150b6f56aa4e59a65750aa115dd
* | Bump up timeouts for DSVM and probe test jobsTim Burke2020-05-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | DSVM recently got a bunch more middlewares enabled, so it's running more tests than it used to. I can't think of much that's changed for probe tests, but I feel like I've seen it popping timeouts more often lately. Note that the new timeouts are still lower than the typical run-time of our longest-running jobs (currently grenade / tempest-ipv6-only). Change-Id: Iffbb567124096df02b04981550faec8204d5d1ec Related-Change: I3cbbcd2ea9ced0923bee4a6b0783e4cf5e82e95b
* | Switch to new grenade job nameAndreas Jaeger2020-05-041-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The integrated gate templates has switched to the new grenade name (grenade-py3 -> grenade). This repo uses an integrated gate template but also listed the job for irrelevant files an extra entry. Rename the job following the template change to avoid duplicate grenade runs. Details: - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014602.html Change-Id: I4afc73301965b582fd338012f0ddc60f9b85fbb0
* | Add stable/ussuri upgrade jobTim Burke2020-04-241-0/+7
| | | | | | | | Change-Id: Ie1c82a80b18dc4f66d3e79fe6e7dbd5d2891c65e
* | Merge "Add experimental job to upgrade from master"Zuul2020-04-241-0/+8
|\ \
| * | Add experimental job to upgrade from masterTim Burke2020-04-221-0/+8
| |/ | | | | | | | | | | | | This should help us catch when a release would break the upgrade-from-most-recent-tag job. Change-Id: I2cc44f57032ebd3e7c8d4443c90b151f4d0c953c
* | Make rolling-upgrade job non-votingTim Burke2020-04-201-0/+2
|/ | | | | | | | 2.25.0 has a test that will leave some account metadata that causes other tests to fail. Change-Id: I986f55707dba3501814ab46d3907357d7c63e4f9 Related-Change: Ifb1d091e58b9331b027edf981f6af5c015b56936
* Revert "Make rolling-upgrade job non-voting until virtualenv problem is solved"Tim Burke2020-02-191-1/+0
| | | | | | | | This reverts commit cd4ba90cc1a13c94e2a02f1af015e20d6882e05f. The virtualenv problem seems to have been resolved. Change-Id: Icae429b4eba796328e767317e204ca30cc105da8
* Make rolling-upgrade job non-voting until virtualenv problem is solvedTim Burke2020-02-131-0/+1
| | | | Change-Id: I4c8a3756afccb2b42acbd9aeac5908f3d4febcae
* Merge "Add py38 unit test job"Zuul2020-01-301-0/+24
|\
| * Add py38 unit test jobTim Burke2019-11-121-0/+24
| | | | | | | | | | Depends-On: https://review.opendev.org/#/c/688594/ Change-Id: Idf6c492d554a3ac3d38bd9dfc9c89494cae82bb1
* | Bump up ceph tests timeoutTim Burke2020-01-221-0/+1
| | | | | | | | | | | | | | | | Looking at the last few hundred runs, we've had ~8% TIMEOUTs, and the average time is already 21 minutes. Let's give it an extra 10 minutes, see if the TIMEOUT rate comes down. Change-Id: Ifd9fbac032825bae1c8f5edd88c5d692a0b2cef1
* | Update list of experimental upgrade testsThiago da Silva2019-12-111-7/+7
| | | | | | | | | | | | Removed test of upgrade from queens and added train Change-Id: Iadab0f87d6fd66fe49c79ee200d175f9bed92baa
* | Switch py2 DSVM jobs to only run swift under py2Tim Burke2019-11-191-0/+4
|/ | | | | | | Other services are fine to move on to py3. We still want to test py2, though. Change-Id: I488f88a54948663c682b35dc976b62db6e72eef7
* Merge "Make our py2 func tests more explicitly py2"Zuul2019-11-051-24/+24
|\
| * Make our py2 func tests more explicitly py2Tim Burke2019-11-051-24/+24
| | | | | | | | | | | | ...because otherwise, I think they might be running under py3 right now. Change-Id: I96ad9e5ed87a7e08d06e889233730cec476d3af7
* | pin lower-constraints to run against python 2.7Thiago da Silva2019-11-011-0/+2
|/ | | | Change-Id: I5c856012a04ef8f910c28b0248ea7bcda47e4816
* Start building py3 docker imagesThiago da Silva2019-10-041-0/+41
| | | | Change-Id: Id6f1075b2774536bb095de0904a1cdcf2b34b0fd
* Add experimental job to test upgrades from steinTim Burke2019-09-281-0/+7
| | | | | | | Also, correct the version that we check out when upgrading from stable branches. Change-Id: Ie733bc50466c66d6e6eb5c6bd42e42a05ef88798
* Merge "Make ceph tests more portable"Zuul2019-09-251-0/+1
|\
| * Make ceph tests more portableClay Gerrard2019-09-131-0/+1
| | | | | | | | Change-Id: If93325f2651a02f98f9d480c10bf7b849cc9617e
* | [train][goal] Run 'tempest-ipv6-only' job in gateGhanshyam Mann2019-09-171-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1], Tempest has defined the new job 'tempest-ipv6-only'(adding in Depends-On patch) which will deploy services on IPv6 and run smoke tests and IPv6 related tests present in Tempest. This job will be part of Nova, Neutron, Cinder, Keystone, Glance, Swift gate. Verification structure will be: - 'devstack-IPv6' deploy the service on IPv6 - 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address - 'tempest-ipv6-only' will run the smoke + IPv6 related test case. This commit adds the new job 'tempest-ipv6-only' run on gate. Story: #2005477 Task: #35932 [1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html Change-Id: I78be2ee5a7f1e5d3188ece98d7d8324f1c9bd0e3
* | Remove unneeded Zuul branch matcherAndreas Jaeger2019-09-131-1/+0
|/ | | | | | | | | | | We have implicit branch matchers, so there's no need to add a check for not-ocata etc, a job is only run for the branch it's on - like master now. Remove it to not confuse Zuul when multiple branches matches and the job definition is different. Change-Id: I6a346c9141aad1aa8a7393c899d5571057073e7a
* py3: Switch swift-dsvm-functional-py3 to run tests under py3Tim Burke2019-08-221-1/+3
| | | | | | Now that all of the func tests are ported, we may as well run all-py3. Change-Id: Ib9f75ca9efb46dc4c7730ad2718228ec7777c924
* py3: mostly port s3 func testsTim Burke2019-08-091-0/+18
| | | | | | test_bucket.py is proving somewhat problematic. Change-Id: I5b337ef66a23fc989762801dd6a5ba1ed903f57b
* Merge "py3: Add swift-tox-func-encryption-py37 gate job"Zuul2019-08-091-0/+18
|\
| * py3: Add swift-tox-func-encryption-py37 gate jobTim Burke2019-08-061-0/+18
| | | | | | | | Change-Id: Ia9ae0fc226dfc9b40157faebac100c10a9180c62
* | Bring our IPv6 setup more in line with devstack'sTim Burke2019-08-081-2/+1
|/ | | | Change-Id: I4a32239eec37eed4085fbc2a283def4b69c816ac
* Add integrated gate tempest and grenade jobGhanshyam Mann2019-07-261-0/+21
| | | | | | | | | | | | | | | | | | Swift gate does not run integrated-gate jobs which are tempest-full and grenade-py3 job. Tempest-full job run all services tests. But all services tests are not needed to run on swift gate because it does not depends on all services. Tempest has prepared the new jobs for swift gate which will run only Swift, Cinder and Glance related tests. New template 'integrated-gate-object-storage'(Depends-On) includes the tempest-integrated-object-storage and grenade-py3 jobs This commit adds the new integrated-gate template in swift gate. Depends-On: https://review.opendev.org/#/c/670353/ Change-Id: Ia0543dca729c3a2aa67ce9f560c1ce5976c00abf
* Merge "Make rolling-upgrade job voting again"Zuul2019-07-241-1/+0
|\
| * Make rolling-upgrade job voting againTim Burke2019-07-171-1/+0
| | | | | | | | | | | | Now that os-testr has had a release, it passes again. Change-Id: Ieed88646d97ab2a1c7323a147ee97dae6fc86a0f
* | Merge "Make py36 job voting"Zuul2019-07-231-1/+1
|\ \
| * | Make py36 job votingTim Burke2019-05-031-1/+1
| | | | | | | | | | | | Change-Id: I4768fe41d6347bcae44774730350f4be583bdf15
* | | py3: Bring functional/test_object.py under test; add func-ec-py37 jobTim Burke2019-07-181-6/+32
| |/ |/| | | | | Change-Id: I2929ce1f8e08ae5b4059605d09189c8521852423
* | Merge "py3: port staticweb and domain_remap func tests"Zuul2019-07-111-0/+18
|\ \
| * | py3: port staticweb and domain_remap func testsTim Burke2019-07-101-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | Drive-by: Tighten domain_remap assertions on listings, which required that we fix proxy pipeline placement. Add a note about it to the sample config. Change-Id: I41835148051294088a2c0fb4ed4e7a7b61273e5f
* | | Run all func tests under py2 against services running py3Tim Burke2019-06-211-3/+1
| | | | | | | | | | | | | | | | | | | | | ... at least, on the py3 dsvm job. Depends-On: I0f03c211f35a9a49e047a5718a9907b515ca88d7 Change-Id: Ia783ae10344380eb5afd9d43273969b433962945
* | | py3: add swift-dsvm-functional-py3 jobTim Burke2019-06-211-0/+24
|/ / | | | | | | | | | | | | | | | | | | Note that keystone wants to stick some UTF-8 encoded bytes into memcached, but we want to store it as JSON... or something? Also, make sure we can hit memcache for containers with invalid UTF-8. Although maybe it'd be better to catch that before we ever try memcache? Change-Id: I1fbe133c8ec73ef6644ecfcbb1931ddef94e0400
* | Merge "Add py37 func test job"Zuul2019-05-201-0/+21
|\ \
| * | Add py37 func test jobTim Burke2019-05-081-0/+21
| | | | | | | | | | | | | | | | | | | | | Make a new func-py3 tox env that will use whatever version of py3 is available, and set up a new check/gate job that runs it under py37. Change-Id: I1ef233276697be994494ed858e88ce97634f814e
View Lorry Controller Status