wbrawner/toolbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
toolbox/.zuul.yaml

68 lines
1.8 KiB
YAML
Raw Normal View History

Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
---
- job:
Connect Go unit tests to Meson & rename CI job We now have some Go unit tests[0] and we should use them. By adding a new test case to Meson, the existing CI job called "shellcheck" has no longer an accurate name. With this it has been renamed to "unit-test". Also, the job is now more important and therefore should also be used for gating. [0] https://github.com/containers/toolbox/pull/474 https://github.com/containers/toolbox/pull/730
2021-03-21 21:01:42 +00:00
name: unit-test
description: Run Toolbox's unit tests declared in Meson
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
timeout: 300
.zuul: Run tests only for relevant files Not all file are equal when it comes to testing. Unit tests are related strictly to the source code and documentation changes do not concern it. System tests have a wider range of influence but documentation and some other areas also do not concern them. I'm unsure about the effect of this change on the periodic pipeline execution. https://github.com/containers/toolbox/pull/948
2021-11-11 22:16:07 +00:00
files: ['playbooks/*', 'src/*', 'meson.build', 'meson_options.txt', '.zuul.yaml']
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
nodeset:
nodes:
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- name: ci-node-34
label: cloud-fedora-34-small
playbooks: Unify test setup for system & unit tests There is no significant benefit in keeping this configuration separated. Now the to-be installed packages are tracked in a single place and the test playbooks only call the relevant tests. This was pointed out by in 6063eb27b98939942e316771224c5653a9b2e59b https://github.com/containers/toolbox/pull/898
2021-10-22 12:21:41 +00:00
pre-run: playbooks/setup-env.yaml
Connect Go unit tests to Meson & rename CI job We now have some Go unit tests[0] and we should use them. By adding a new test case to Meson, the existing CI job called "shellcheck" has no longer an accurate name. With this it has been renamed to "unit-test". Also, the job is now more important and therefore should also be used for gating. [0] https://github.com/containers/toolbox/pull/474 https://github.com/containers/toolbox/pull/730
2021-03-21 21:01:42 +00:00
run: playbooks/unit-test.yaml
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
zuul, playbooks: Enable system tests on Fedora 33 https://github.com/containers/toolbox/pull/550
2020-08-31 12:12:34 +00:00
- job:
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
name: system-test-fedora-34
description: Run Toolbox's system tests in Fedora 34
zuul, playbooks: Enable system tests on Fedora 33 https://github.com/containers/toolbox/pull/550
2020-08-31 12:12:34 +00:00
timeout: 1200
.zuul: Run tests only for relevant files Not all file are equal when it comes to testing. Unit tests are related strictly to the source code and documentation changes do not concern it. System tests have a wider range of influence but documentation and some other areas also do not concern them. I'm unsure about the effect of this change on the periodic pipeline execution. https://github.com/containers/toolbox/pull/948
2021-11-11 22:16:07 +00:00
files: &system_test_files ['data/*', 'playbooks/*', 'profile.d/*', 'src/*', 'meson.build', 'meson_options.txt', '.zuul.yaml']
zuul, playbooks: Enable system tests on Fedora 33 https://github.com/containers/toolbox/pull/550
2020-08-31 12:12:34 +00:00
nodeset:
nodes:
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- name: ci-node-34
label: cloud-fedora-34-small
.zuul, playbooks: Unify the setup-env.yaml across all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/701
2021-02-19 16:25:08 +00:00
pre-run: playbooks/setup-env.yaml
.zuul, playbooks: Unify the system-test*.yaml for all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/702
2021-02-19 17:47:08 +00:00
run: playbooks/system-test.yaml
zuul, playbooks: Enable system tests on Fedora 33 https://github.com/containers/toolbox/pull/550
2020-08-31 12:12:34 +00:00
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
- job:
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
name: system-test-fedora-35
description: Run Toolbox's system tests in Fedora 35
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
timeout: 1200
.zuul: Run tests only for relevant files Not all file are equal when it comes to testing. Unit tests are related strictly to the source code and documentation changes do not concern it. System tests have a wider range of influence but documentation and some other areas also do not concern them. I'm unsure about the effect of this change on the periodic pipeline execution. https://github.com/containers/toolbox/pull/948
2021-11-11 22:16:07 +00:00
files: *system_test_files
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
nodeset:
nodes:
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- name: ci-node-35
label: cloud-fedora-35-small
.zuul, playbooks: Unify the setup-env.yaml across all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/701
2021-02-19 16:25:08 +00:00
pre-run: playbooks/setup-env.yaml
.zuul, playbooks: Unify the system-test*.yaml for all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/702
2021-02-19 17:47:08 +00:00
run: playbooks/system-test.yaml
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
- job:
playbooks, .zuul: Clarify naming and descriptions Not all tests are the same and the ones we're currently running are system tests. Also the mention of 'podman-stable' is not that important because we're using the version in the 'stable' stream of Fedora releases. https://github.com/containers/toolbox/pull/508
2020-07-15 10:42:04 +00:00
name: system-test-fedora-rawhide
description: Run Toolbox's system tests in Fedora Rawhide
.zuul: Try to prevent the CI from timing out on Fedora Rawhide Currently, the CI has been frequently timing out on Fedora Rawhide nodes, and it's not clear why that is. One possibility is that this is due to Rawhide using Linux kernels that are built with debugging enabled, which makes it slower than released Fedoras. So it might be a matter of just increasing the timeout. Currently, the timeout for stable Fedoras is 20 minutes, and that for Rawhide is 22 minutes. An attempt to increase the Rawhide timeout to 30 minutes didn't succeed, so maybe 45 minutes will be sufficient. https://github.com/containers/toolbox/pull/964
2021-12-17 13:30:34 +00:00
timeout: 2700
.zuul: Run tests only for relevant files Not all file are equal when it comes to testing. Unit tests are related strictly to the source code and documentation changes do not concern it. System tests have a wider range of influence but documentation and some other areas also do not concern them. I'm unsure about the effect of this change on the periodic pipeline execution. https://github.com/containers/toolbox/pull/948
2021-11-11 22:16:07 +00:00
files: *system_test_files
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
nodeset:
nodes:
- name: ci-node-rawhide
label: cloud-fedora-rawhide-small
.zuul, playbooks: Unify the setup-env.yaml across all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/701
2021-02-19 16:25:08 +00:00
pre-run: playbooks/setup-env.yaml
.zuul, playbooks: Unify the system-test*.yaml for all Fedora versions The playbooks were too fragmented and were hard to maintain. With this the number of files is significantly lowered. https://github.com/containers/toolbox/pull/517 https://github.com/containers/toolbox/pull/702
2021-02-19 17:47:08 +00:00
run: playbooks/system-test.yaml
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
- project:
periodic:
jobs:
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
- system-test-fedora-34
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- system-test-fedora-35
playbooks, .zuul: Clarify naming and descriptions Not all tests are the same and the ones we're currently running are system tests. Also the mention of 'podman-stable' is not that important because we're using the version in the 'stable' stream of Fedora releases. https://github.com/containers/toolbox/pull/508
2020-07-15 10:42:04 +00:00
- system-test-fedora-rawhide
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
check:
jobs:
Connect Go unit tests to Meson & rename CI job We now have some Go unit tests[0] and we should use them. By adding a new test case to Meson, the existing CI job called "shellcheck" has no longer an accurate name. With this it has been renamed to "unit-test". Also, the job is now more important and therefore should also be used for gating. [0] https://github.com/containers/toolbox/pull/474 https://github.com/containers/toolbox/pull/730
2021-03-21 21:01:42 +00:00
- unit-test
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
- system-test-fedora-34
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- system-test-fedora-35
playbooks, .zuul: Clarify naming and descriptions Not all tests are the same and the ones we're currently running are system tests. Also the mention of 'podman-stable' is not that important because we're using the version in the 'stable' stream of Fedora releases. https://github.com/containers/toolbox/pull/508
2020-07-15 10:42:04 +00:00
- system-test-fedora-rawhide
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68
2019-09-03 13:31:38 +00:00
gate:
jobs:
Connect Go unit tests to Meson & rename CI job We now have some Go unit tests[0] and we should use them. By adding a new test case to Meson, the existing CI job called "shellcheck" has no longer an accurate name. With this it has been renamed to "unit-test". Also, the job is now more important and therefore should also be used for gating. [0] https://github.com/containers/toolbox/pull/474 https://github.com/containers/toolbox/pull/730
2021-03-21 21:01:42 +00:00
- unit-test
ci: Enable testing on Fedora 34
2021-02-17 12:39:40 +00:00
- system-test-fedora-34
.zuul: pump the current fedora releases to 34 & 35 F33 will EOL at the end of this month (Nov 2021) https://github.com/containers/toolbox/pull/927
2021-11-16 09:24:14 +00:00
- system-test-fedora-35
playbooks, .zuul: Clarify naming and descriptions Not all tests are the same and the ones we're currently running are system tests. Also the mention of 'podman-stable' is not that important because we're using the version in the 'stable' stream of Fedora releases. https://github.com/containers/toolbox/pull/508
2020-07-15 10:42:04 +00:00
- system-test-fedora-rawhide
Reference in a new issue Copy permalink