-
Notifications
You must be signed in to change notification settings - Fork 1
216 lines (203 loc) · 7.98 KB
/
ansible-test.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
---
name: CI
on:
# Run CI against all pushes (direct commits, also merged PRs), Pull Requests
push:
branches:
- main
- stable-*
pull_request:
# Run CI once per day (at 06:00 UTC)
# This ensures that even if there haven't been commits that we are still
# testing against latest version of ansible-test for each ansible-core
# version
schedule:
- cron: "0 6 * * *"
workflow_call:
concurrency:
group: >-
${{ github.workflow }}-${{
github.event.pull_request.number || github.sha
}}
cancel-in-progress: true
jobs:
###
# Sanity tests (REQUIRED)
#
# https://docs.ansible.com/ansible/latest/dev_guide/testing_sanity.html
sanity:
name: Sanity (Ⓐ${{ matrix.ansible }})
strategy:
matrix:
ansible:
- stable-2.16
- stable-2.17
- devel
runs-on: >-
${{ contains(fromJson(
'["stable-2.9", "stable-2.10", "stable-2.11"]'
), matrix.ansible) && 'ubuntu-20.04' || 'ubuntu-latest' }}
steps:
- name: Perform sanity testing
# See the documentation for the following GitHub action on
# https://github.com/ansible-community/ansible-test-gh-action/blob/main/README.md
uses: ansible-community/ansible-test-gh-action@release/v1
with:
ansible-core-version: ${{ matrix.ansible }}
testing-type: sanity
# OPTIONAL If your sanity tests require code
# from other collections, install them like this
# test-deps: >-
# ansible.netcommon
# ansible.utils
# OPTIONAL If set to true, will test only against changed files,
# which should improve CI performance. See limitations on
# https://github.com/ansible-community/ansible-test-gh-action#pull-request-change-detection
pull-request-change-detection: false
###
# Unit tests (OPTIONAL)
#
# https://docs.ansible.com/ansible/latest/dev_guide/testing_units.html
#
# units:
# # Ansible-test on various stable branches does not yet work well with cgroups v2.
# # Since ubuntu-latest now uses Ubuntu 22.04, we need to fall back to the ubuntu-20.04
# # image for these stable branches. The list of branches where this is necessary will
# # shrink over time, check out https://github.com/ansible-collections/news-for-maintainers/issues/28
# # for the latest list.
# runs-on: >-
# ${{ contains(fromJson(
# '["stable-2.9", "stable-2.10", "stable-2.11"]'
# ), matrix.ansible) && 'ubuntu-20.04' || 'ubuntu-latest' }}
# name: Units (Ⓐ${{ matrix.ansible }})
# strategy:
# # As soon as the first unit test fails, cancel the others to free up the CI queue
# fail-fast: true
# matrix:
# ansible:
# # Add new versions announced in
# # https://github.com/ansible-collections/news-for-maintainers in a timely manner,
# # consider dropping testing against EOL versions and versions you don't support.
# - stable-2.15
# - stable-2.16
# - stable-2.17
# - devel
# # - milestone
#
# steps:
# - name: >-
# Perform unit testing against
# Ansible version ${{ matrix.ansible }}
# # See the documentation for the following GitHub action on
# # https://github.com/ansible-community/ansible-test-gh-action/blob/main/README.md
# uses: ansible-community/ansible-test-gh-action@release/v1
# with:
# ansible-core-version: ${{ matrix.ansible }}
# testing-type: units
# # OPTIONAL If your unit tests require code
# # from other collections, install them like this
# test-deps: >-
# ansible.netcommon
# ansible.utils
# # OPTIONAL If set to true, will test only against changed files,
# # which should improve CI performance. See limitations on
# # https://github.com/ansible-community/ansible-test-gh-action#pull-request-change-detection
# pull-request-change-detection: false
###
# Integration tests (RECOMMENDED)
#
# https://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html
# If the application you are testing is available as a docker container and you want to test
# multiple versions see the following for an example:
# https://github.com/ansible-collections/community.zabbix/tree/master/.github/workflows
integration:
# Ansible-test on various stable branches does not yet work well with cgroups v2.
# Since ubuntu-latest now uses Ubuntu 22.04, we need to fall back to the ubuntu-20.04
# image for these stable branches. The list of branches where this is necessary will
# shrink over time, check out https://github.com/ansible-collections/news-for-maintainers/issues/28
# for the latest list.
runs-on: >-
${{ contains(fromJson(
'["stable-2.9", "stable-2.10", "stable-2.11"]'
), matrix.ansible) && 'ubuntu-20.04' || 'ubuntu-latest' }}
name: I (Ⓐ${{ matrix.ansible }}+py${{ matrix.python }})
strategy:
fail-fast: false
matrix:
ansible:
- devel
# - milestone
python:
- "3.11"
- "3.12"
include:
# Add new versions announced in
# https://github.com/ansible-collections/news-for-maintainers in a timely manner,
# consider dropping testing against EOL versions and versions you don't support.
# ansible-core 2.16
- ansible: stable-2.16
python: "3.10"
- ansible: stable-2.16
python: "3.11"
- ansible: stable-2.16
python: "3.12"
# ansible-core 2.17
- ansible: stable-2.17
python: "3.10"
- ansible: stable-2.17
python: "3.11"
- ansible: stable-2.17
python: "3.12"
steps:
- name: >-
Perform integration testing against
Ansible version ${{ matrix.ansible }}
under Python ${{ matrix.python }}
# See the documentation for the following GitHub action on
# https://github.com/ansible-community/ansible-test-gh-action/blob/main/README.md
uses: ansible-community/ansible-test-gh-action@release/v1
with:
ansible-core-version: ${{ matrix.ansible }}
# OPTIONAL command to run before invoking `ansible-test integration`
pre-test-cmd: pip install cryptography
target-python-version: ${{ matrix.python }}
testing-type: integration
# OPTIONAL If your integration tests require code
# from other collections, install them like this
test-deps: >-
ansible.netcommon
community.crypto
# OPTIONAL If set to true, will test only against changed files,
# which should improve CI performance. See limitations on
# https://github.com/ansible-community/ansible-test-gh-action#pull-request-change-detection
pull-request-change-detection: false
build:
runs-on: ubuntu-latest
steps:
- name: Perform integration for build
uses: ansible-community/ansible-test-gh-action@release/v1
with:
ansible-core-version: stable-2.17
target-python-version: "3.10"
testing-type: integration
test-deps: >-
ansible.netcommon
community.crypto
pull-request-change-detection: false
- name: Build collection
run: ansible-galaxy collection build ansible_collections/mgit_at/mgssl/ --force
check: # This job does nothing and is only used for the branch protection
# or multi-stage CI jobs, like making sure that all tests pass before
# a publishing job is started.
if: always()
needs:
- sanity
# - units
- integration
- build
runs-on: ubuntu-latest
steps:
- name: Decide whether the needed jobs succeeded or failed
uses: re-actors/alls-green@release/v1
with:
jobs: ${{ toJSON(needs) }}