atomic-desktops/ci-test
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-test/ci/validate.yaml

98 lines
3.7 KiB
YAML
Raw Normal View History

zuul: Fix YAML indentation
2024-03-01 18:32:37 +00:00
- hosts: all
tasks:
ci: Update all pacakges on the system first
2024-06-13 08:46:46 +00:00
- name: Upgrade all packages
ansible.builtin.dnf:
name: "*"
state: latest
become: true
zuul: Fix YAML indentation
2024-03-01 18:32:37 +00:00
- name: Install dependencies
package:
name:
- 'jq'
- 'just'
- 'ostree'
- 'python3-pyyaml'
- 'rpm-ostree'
- 'selinux-policy-targeted'
state: present
ci: Fix yaml lint
2024-03-01 18:37:01 +00:00
become: true
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
zuul: Fix YAML indentation
2024-03-01 18:32:37 +00:00
- name: Validate manifests and scripts syntax
ansible.builtin.command:
chdir: "{{ zuul.project.src_dir }}"
cmd: just validate
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
zuul: Verify that the comps and manifests are synced Best effort (as it will only run on PRs) check for comps / manifests sync.
2024-03-28 17:12:37 +00:00
- name: Verify that the comps and manifests are synced
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just validate comps-sync-check && touch .zuulci.comps"
# Still run the next step if this one fails
ignore_errors: true
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
- name: Perform dependency resolution for Silverblue
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run silverblue && touch .zuulci.silverblue"
# Still run the next step if this one fails
ignore_errors: true
ci: Check dependency resolution for classic ostree variants With the split between classic ostree variants and the Bootable Container ones, we are starting to diverge in package set for those images. Make sure to validate dependency resolution for both variants.
2024-07-26 15:14:40 +00:00
- name: Perform dependency resolution for Silverblue (ostree classic)
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run silverblue-ostree && touch .zuulci.silverblue-ostree"
# Still run the next step if this one fails
ignore_errors: true
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
- name: Perform dependency resolution for Kinoite
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run kinoite && touch .zuulci.kinoite"
# Still run the next step if this one fails
ignore_errors: true
ci: Check dependency resolution for classic ostree variants With the split between classic ostree variants and the Bootable Container ones, we are starting to diverge in package set for those images. Make sure to validate dependency resolution for both variants.
2024-07-26 15:14:40 +00:00
- name: Perform dependency resolution for Kinoite (ostree classic)
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run kinoite-ostree && touch .zuulci.kinoite-ostree"
# Still run the next step if this one fails
ignore_errors: true
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
- name: Perform dependency resolution for Sway Atomic
ansible.builtin.shell:
zuul: Fix YAML indentation
2024-03-01 18:32:37 +00:00
chdir: "{{ zuul.project.src_dir }}"
Use new Atomic names
2024-06-11 13:19:53 +00:00
cmd: "just compose-dry-run sway-atomic && touch .zuulci.sway-atomic"
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
# Still run the next step if this one fails
ignore_errors: true
ci: Check dependency resolution for classic ostree variants With the split between classic ostree variants and the Bootable Container ones, we are starting to diverge in package set for those images. Make sure to validate dependency resolution for both variants.
2024-07-26 15:14:40 +00:00
- name: Perform dependency resolution for Sway Atomic (ostree classic)
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run sway-atomic-ostree && touch .zuulci.sway-atomic-ostree"
# Still run the next step if this one fails
ignore_errors: true
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
- name: Perform dependency resolution for Budgie Atomic
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
Use new Atomic names
2024-06-11 13:19:53 +00:00
cmd: "just compose-dry-run budgie-atomic && touch .zuulci.budgie-atomic"
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
# Still run the next step if this one fails
ignore_errors: true
ci: Check dependency resolution for classic ostree variants With the split between classic ostree variants and the Bootable Container ones, we are starting to diverge in package set for those images. Make sure to validate dependency resolution for both variants.
2024-07-26 15:14:40 +00:00
- name: Perform dependency resolution for Budgie Atomic (ostree classic)
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
cmd: "just compose-dry-run budgie-atomic-ostree && touch .zuulci.budgie-atomic-ostree"
# Still run the next step if this one fails
ignore_errors: true
zuul: Fix YAML indentation
2024-03-01 18:32:37 +00:00
- name: Compose the base variant
ansible.builtin.command:
chdir: "{{ zuul.project.src_dir }}"
ci/validate: Test by building a Bootable Container Switch to building a bootable container by default.
2024-06-11 14:50:42 +00:00
cmd: just compose-image base-atomic
ci: Split dependency check and run checks all on failures - Split the dependency check into a distinct step for each variant - If the dependency test failed, still run the compose base test to get results about it - Add a step at the end to make sure that if any step fails, the workflow still fail See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#ignoring-failed-commands See discussion in: https://pagure.io/workstation-ostree-config/pull-request/493
2024-03-01 17:30:47 +00:00
- name: Check if any previous dependency resolution steps failed
ansible.builtin.shell:
chdir: "{{ zuul.project.src_dir }}"
ci: Check dependency resolution for classic ostree variants With the split between classic ostree variants and the Bootable Container ones, we are starting to diverge in package set for those images. Make sure to validate dependency resolution for both variants.
2024-07-26 15:14:40 +00:00
cmd: "[[ -f .zuulci.comps ]] && [[ -f .zuulci.silverblue ]] && [[ -f .zuulci.silverblue-ostree ]] && [[ -f .zuulci.kinoite ]] && [[ -f .zuulci.kinoite-ostree ]] && [[ -f .zuulci.sway-atomic ]] && [[ -f .zuulci.sway-atomic-ostree ]] && [[ -f .zuulci.budgie-atomic ]] && [[ -f .zuulci.budgie-atomic-ostree ]]"
Reference in a new issue Copy permalink