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

120 lines
3.3 KiB
YAML
Raw Permalink Normal View History

.zuul, playbooks: Add copyright and license notices https://github.com/containers/toolbox/pull/1179
2022-11-28 20:09:42 +00:00
#
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
# Copyright © 2020 – 2023 Red Hat, Inc.
.zuul, playbooks: Add copyright and license notices https://github.com/containers/toolbox/pull/1179
2022-11-28 20:09:42 +00:00
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
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
.zuul: Use the latest version of the tools for static analysis The 'unit tests' are no longer just unit tests. They also run a bunch of static analysis tools like ShellCheck, codespell, gofmt and 'go vet'. Since newer versions of these tools are generally better at catching problems in the codebase, it will be better to run the 'unit tests' on Fedora Rawhide with the latest versions than older stable Fedoras. The timeout for the 'unit tests' need to be increased because Fedora Rawhide is slower than stable Fedoras. Currently, the timeout for the 'unit tests' running on Fedora 36 is 10 minutes. Increasing it to 20 minutes when running on Fedora Rawhide wasn't enough, so maybe 30 will be sufficient. Note that this is only feasible because the Fedora Rawhide builds are now more robust against stale DNF caches [1]. Otherwise, it wouldn't have been wise to use Fedora Rawhide to test anything which isn't also being tested elsewhere, because the Fedora Rawhide builds might have stayed broken for extended periods of time due to reasons completely unrelated to Toolbx. [1] Commit 995c6d175ec5f790 https://github.com/containers/toolbox/pull/1201 https://github.com/containers/toolbox/pull/1206
2022-12-19 22:56:33 +00:00
timeout: 1800
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: Use the latest version of the tools for static analysis The 'unit tests' are no longer just unit tests. They also run a bunch of static analysis tools like ShellCheck, codespell, gofmt and 'go vet'. Since newer versions of these tools are generally better at catching problems in the codebase, it will be better to run the 'unit tests' on Fedora Rawhide with the latest versions than older stable Fedoras. The timeout for the 'unit tests' need to be increased because Fedora Rawhide is slower than stable Fedoras. Currently, the timeout for the 'unit tests' running on Fedora 36 is 10 minutes. Increasing it to 20 minutes when running on Fedora Rawhide wasn't enough, so maybe 30 will be sufficient. Note that this is only feasible because the Fedora Rawhide builds are now more robust against stale DNF caches [1]. Otherwise, it wouldn't have been wise to use Fedora Rawhide to test anything which isn't also being tested elsewhere, because the Fedora Rawhide builds might have stayed broken for extended periods of time due to reasons completely unrelated to Toolbx. [1] Commit 995c6d175ec5f790 https://github.com/containers/toolbox/pull/1201 https://github.com/containers/toolbox/pull/1206
2022-12-19 22:56:33 +00:00
- name: fedora-rawhide
label: cloud-fedora-rawhide
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: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095
2022-08-31 11:09:44 +00:00
- job:
name: unit-test-migration-path-for-coreos-toolbox
description: Run Toolbox's unit tests declared in Meson when built with -Dmigration_path_for_coreos_toolbox
timeout: 600
nodeset:
nodes:
Test -Dmigration_path_for_coreos_toolbox on CentOS Stream 9 The code behind -Dmigration_path_for_coreos_toolbox is meant for Red Hat Enterprise Linux 8 and 9. Hence, it makes sense to use CentOS Stream 9 to run the 'unit tests' on the corresponding code path. Note that, just like Fedora, Podman prefers crun(1) as its OCI runtime on CentOS Stream 9 [1,2]. [1] Podman commit 060775901de09b27 https://gitlab.com/redhat/centos-stream/rpms/podman/-/commit/060775901de09b27 [2] Podman commit f327e88a08ca224b https://gitlab.com/redhat/centos-stream/rpms/podman/-/commit/f327e88a08ca224b https://github.com/containers/toolbox/pull/1171
2022-11-18 18:27:36 +00:00
- name: centos-9-stream
label: cloud-centos-9-stream
.zuul, playbooks: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095
2022-08-31 11:09:44 +00:00
pre-run: playbooks/setup-env-migration-path-for-coreos-toolbox.yaml
run: playbooks/unit-test.yaml
Test that toolbox(1) can be built without podman(1) and subordinate IDs This is meant to roughly replicate the build environments used by downstream distributors to build toolbox(1). These can be restricted in odd ways compared to a fully featured environment where toolbox(1) is actually going to be used. eg., the inability to use podman(1) in the case of Fedora or not having subordinate user and group ID ranges in the case of openSUSE. It's important to ensure that toolbox(1) can be built by downstream distributors without any unnecessary hassle. https://github.com/containers/podman/issues/17657 https://github.com/containers/toolbox/issues/1246
2023-03-01 20:03:53 +00:00
- job:
name: unit-test-restricted
description: Run Toolbox's unit tests declared in Meson in a restricted build environment
timeout: 1800
nodeset:
nodes:
- name: fedora-rawhide
label: cloud-fedora-rawhide
pre-run: playbooks/setup-env-restricted.yaml
run: playbooks/unit-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
- job:
.zuul: Shuffle some code around Defining the YAML anchor as part of the Rawhide tests, instead of the Fedora 34 test, will prevent it from getting lost by mistake when Fedora 34 reaches its End of Life. https://github.com/containers/toolbox/pull/971
2022-01-05 01:04:47 +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 With the recent expansion of the test suite, it's necessary to increase the timeout for all Fedora nodes to prevent the CI from timing out. https://github.com/containers/toolbox/pull/1387
2023-10-11 18:44:56 +00:00
timeout: 4800
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: Use less cryptic names for the nodes The name of a node in a nodeset is meant to be a human-readable name. A name with an obscure prefix like 'ci-node-' makes it look more profound than it really is. https://github.com/containers/toolbox/pull/1206
2022-12-20 07:43:26 +00:00
- name: fedora-rawhide
.zuul: Use labels/nodes without the '-small' suffix
2022-03-20 21:18:52 +00:00
label: cloud-fedora-rawhide
.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
.zuul: Enable testing on Fedora 39 https://github.com/containers/toolbox/pull/1385
2023-10-06 10:43:09 +00:00
- job:
name: system-test-fedora-39
description: Run Toolbx's system tests in Fedora 39
.zuul: Try to prevent the CI from timing out on Fedora With the recent expansion of the test suite, it's necessary to increase the timeout for all Fedora nodes to prevent the CI from timing out. https://github.com/containers/toolbox/pull/1387
2023-10-11 18:44:56 +00:00
timeout: 3000
.zuul: Enable testing on Fedora 39 https://github.com/containers/toolbox/pull/1385
2023-10-06 10:43:09 +00:00
nodeset:
nodes:
- name: fedora-39
label: cloud-fedora-39
pre-run: playbooks/setup-env.yaml
run: playbooks/system-test.yaml
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
- job:
name: system-test-fedora-38
description: Run Toolbx's system tests in Fedora 38
.zuul: Try to prevent the CI from timing out on Fedora With the recent expansion of the test suite, it's necessary to increase the timeout for all Fedora nodes to prevent the CI from timing out. https://github.com/containers/toolbox/pull/1387
2023-10-11 18:44:56 +00:00
timeout: 3000
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
nodeset:
nodes:
- name: fedora-38
label: cloud-fedora-38
pre-run: playbooks/setup-env.yaml
run: playbooks/system-test.yaml
.zuul: Enable testing on Fedora 37 https://github.com/containers/toolbox/pull/1237
2023-02-10 20:45:19 +00:00
- job:
name: system-test-fedora-37
description: Run Toolbx's system tests in Fedora 37
.zuul: Try to prevent the CI from timing out on Fedora With the recent expansion of the test suite, it's necessary to increase the timeout for all Fedora nodes to prevent the CI from timing out. https://github.com/containers/toolbox/pull/1387
2023-10-11 18:44:56 +00:00
timeout: 3000
.zuul: Enable testing on Fedora 37 https://github.com/containers/toolbox/pull/1237
2023-02-10 20:45:19 +00:00
nodeset:
nodes:
- name: fedora-37
label: cloud-fedora-37
pre-run: playbooks/setup-env.yaml
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:
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
.zuul: Enable testing on Fedora 39 https://github.com/containers/toolbox/pull/1385
2023-10-06 10:43:09 +00:00
- system-test-fedora-39
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
- system-test-fedora-38
.zuul: Enable testing on Fedora 37 https://github.com/containers/toolbox/pull/1237
2023-02-10 20:45:19 +00:00
- system-test-fedora-37
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
.zuul, playbooks: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095
2022-08-31 11:09:44 +00:00
- unit-test-migration-path-for-coreos-toolbox
Test that toolbox(1) can be built without podman(1) and subordinate IDs This is meant to roughly replicate the build environments used by downstream distributors to build toolbox(1). These can be restricted in odd ways compared to a fully featured environment where toolbox(1) is actually going to be used. eg., the inability to use podman(1) in the case of Fedora or not having subordinate user and group ID ranges in the case of openSUSE. It's important to ensure that toolbox(1) can be built by downstream distributors without any unnecessary hassle. https://github.com/containers/podman/issues/17657 https://github.com/containers/toolbox/issues/1246
2023-03-01 20:03:53 +00:00
- unit-test-restricted
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
.zuul: Enable testing on Fedora 39 https://github.com/containers/toolbox/pull/1385
2023-10-06 10:43:09 +00:00
- system-test-fedora-39
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
- system-test-fedora-38
.zuul: Enable testing on Fedora 37 https://github.com/containers/toolbox/pull/1237
2023-02-10 20:45:19 +00:00
- system-test-fedora-37
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
.zuul, playbooks: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095
2022-08-31 11:09:44 +00:00
- unit-test-migration-path-for-coreos-toolbox
Test that toolbox(1) can be built without podman(1) and subordinate IDs This is meant to roughly replicate the build environments used by downstream distributors to build toolbox(1). These can be restricted in odd ways compared to a fully featured environment where toolbox(1) is actually going to be used. eg., the inability to use podman(1) in the case of Fedora or not having subordinate user and group ID ranges in the case of openSUSE. It's important to ensure that toolbox(1) can be built by downstream distributors without any unnecessary hassle. https://github.com/containers/podman/issues/17657 https://github.com/containers/toolbox/issues/1246
2023-03-01 20:03:53 +00:00
- unit-test-restricted
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
.zuul: Enable testing on Fedora 39 https://github.com/containers/toolbox/pull/1385
2023-10-06 10:43:09 +00:00
- system-test-fedora-39
.zuul: Enable testing on Fedora 38 https://github.com/containers/toolbox/pull/1265
2023-03-16 16:52:23 +00:00
- system-test-fedora-38
.zuul: Enable testing on Fedora 37 https://github.com/containers/toolbox/pull/1237
2023-02-10 20:45:19 +00:00
- system-test-fedora-37
Reference in a new issue Copy permalink