|
1 | 1 | # README FIRST
|
2 |
| -# 1. If you don't have unit tests, remove that section. |
3 |
| -# 2. If your collection depends on other collections ensure they are installed, |
| 2 | +# 1. Subscribe to https://github.com/ansible-collections/news-for-maintainers |
| 3 | +# (click the Watch button on the homepage > Custom > Issues) |
| 4 | +# and keep this matrix up to date in accordance to related announcements. |
| 5 | +# Timely add new ansible-core versions and consider dropping support |
| 6 | +# and testing against its EOL versions. |
| 7 | +# 2. If your collection repository is under the ansible-collections org, |
| 8 | +# please keep in mind that the number of GHA jobs is limited |
| 9 | +# and shared across all the collections in the org. |
| 10 | +# So, focusing on good test coverage of your collection, |
| 11 | +# please avoid testing against unnecessary entities such as |
| 12 | +# ansible-core EOL versions your collection does not support |
| 13 | +# or ansible-core versions that are not EOL yet but not supported by the collection. |
| 14 | +# 3. If you don't have unit or integration tests, remove corresponding sections. |
| 15 | +# 4. If your collection depends on other collections ensure they are installed, |
4 | 16 | # add them to the "test-deps" input.
|
5 |
| -# 3. For the comprehensive list of the inputs supported by the |
| 17 | +# 5. For the comprehensive list of the inputs supported by the |
6 | 18 | # ansible-community/ansible-test-gh-action GitHub Action, see
|
7 | 19 | # https://github.com/marketplace/actions/ansible-test.
|
8 |
| -# 4. If you want to prevent merging PRs that do not pass all tests, |
| 20 | +# 6. If you want to prevent merging PRs that do not pass all tests, |
9 | 21 | # make sure to add the "check" job to your repository branch
|
10 | 22 | # protection once this workflow is added.
|
11 | 23 | # It is also possible to tweak which jobs are allowed to fail. See
|
12 | 24 | # https://github.com/marketplace/actions/alls-green#gotchas for more detail.
|
13 |
| -# 5. If you need help please ask in #ansible-community on the Libera.chat IRC |
14 |
| -# network. |
| 25 | +# 7. If you need help please ask in #community:ansible.com on Matrix |
| 26 | +# or in bridged #ansible-community on the Libera.Chat IRC channel. |
| 27 | +# See https://docs.ansible.com/ansible/devel/community/communication.html |
| 28 | +# for details. |
| 29 | +# 8. If your collection is [going to get] included in the Ansible package, |
| 30 | +# it has to adhere to Python compatibility and CI testing requirements described in |
| 31 | +# https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html. |
15 | 32 |
|
16 | 33 | name: CI
|
17 | 34 | on:
|
|
55 | 72 | # around creation of a new stable branch, this might cause a problem
|
56 | 73 | # that two different versions of ansible-test use the same sanity test
|
57 | 74 | # ignore.txt file.
|
58 |
| - # The commented branches below are EOL, |
59 |
| - # do you really need your collection to support them if it still does? |
60 |
| - # - stable-2.9 # Only if your collection supports Ansible 2.9 |
61 |
| - # - stable-2.10 # Only if your collection supports ansible-base 2.10 |
62 |
| - # - stable-2.11 # Only if your collection supports ansible-core 2.11 |
63 |
| - # - stable-2.12 # Only if your collection supports ansible-core 2.12 |
| 75 | + # Add new versions announced in |
| 76 | + # https://github.com/ansible-collections/news-for-maintainers in a timely manner, |
| 77 | + # consider dropping testing against EOL versions and versions you don't support. |
64 | 78 | - stable-2.13
|
65 | 79 | - stable-2.14
|
66 | 80 | - stable-2.15
|
@@ -117,12 +131,9 @@ jobs:
|
117 | 131 | fail-fast: true
|
118 | 132 | matrix:
|
119 | 133 | ansible:
|
120 |
| - # The commented branches below are EOL, |
121 |
| - # do you really need your collection to support them if it still does? |
122 |
| - # - stable-2.9 # Only if your collection supports Ansible 2.9 |
123 |
| - # - stable-2.10 # Only if your collection supports ansible-base 2.10 |
124 |
| - # - stable-2.11 # Only if your collection supports ansible-core 2.11 |
125 |
| - # - stable-2.12 # Only if your collection supports ansible-core 2.12 |
| 134 | + # Add new versions announced in |
| 135 | + # https://github.com/ansible-collections/news-for-maintainers in a timely manner, |
| 136 | + # consider dropping testing against EOL versions and versions you don't support. |
126 | 137 | - stable-2.13
|
127 | 138 | - stable-2.14
|
128 | 139 | - stable-2.15
|
@@ -185,71 +196,9 @@ jobs:
|
185 | 196 | - '3.10'
|
186 | 197 | - '3.11'
|
187 | 198 | include:
|
188 |
| - # Add more CI runs for specific ansible-core + Python combinations |
189 |
| - |
190 |
| - # The commented branches below are EOL, |
191 |
| - # do you really need your collection to support them if it still does? |
192 |
| - |
193 |
| - # Ansible 2.9 - only if your collection supports Ansible 2.9! |
194 |
| - # - ansible: stable-2.9 |
195 |
| - # python: '2.6' |
196 |
| - # - ansible: stable-2.9 |
197 |
| - # python: '2.7' |
198 |
| - # - ansible: stable-2.9 |
199 |
| - # python: '3.5' |
200 |
| - # - ansible: stable-2.9 |
201 |
| - # python: '3.6' |
202 |
| - # - ansible: stable-2.9 |
203 |
| - # python: '3.7' |
204 |
| - # - ansible: stable-2.9 |
205 |
| - # python: '3.8' |
206 |
| - # ansible-base 2.10 - only if your collection supports ansible 2.10! |
207 |
| - # - ansible: stable-2.10 |
208 |
| - # python: '2.6' |
209 |
| - # - ansible: stable-2.10 |
210 |
| - # python: '2.7' |
211 |
| - # - ansible: stable-2.10 |
212 |
| - # python: '3.5' |
213 |
| - # - ansible: stable-2.10 |
214 |
| - # python: '3.6' |
215 |
| - # - ansible: stable-2.10 |
216 |
| - # python: '3.7' |
217 |
| - # - ansible: stable-2.10 |
218 |
| - # python: '3.8' |
219 |
| - # - ansible: stable-2.10 |
220 |
| - # python: '3.9' |
221 |
| - # ansible-core 2.11 - only if your collection supports ansible 2.11! |
222 |
| - # - ansible: stable-2.11 |
223 |
| - # python: '2.6' |
224 |
| - # - ansible: stable-2.11 |
225 |
| - # python: '2.7' |
226 |
| - # - ansible: stable-2.11 |
227 |
| - # python: '3.5' |
228 |
| - # - ansible: stable-2.11 |
229 |
| - # python: '3.6' |
230 |
| - # - ansible: stable-2.11 |
231 |
| - # python: '3.7' |
232 |
| - # - ansible: stable-2.11 |
233 |
| - # python: '3.8' |
234 |
| - # - ansible: stable-2.11 |
235 |
| - # python: '3.9' |
236 |
| - # ansible-core 2.12 - only if your collection supports ansible 2.12! |
237 |
| - # - ansible: stable-2.12 |
238 |
| - # python: '2.6' |
239 |
| - # - ansible: stable-2.12 |
240 |
| - # python: '2.7' |
241 |
| - # - ansible: stable-2.12 |
242 |
| - # python: '3.5' |
243 |
| - # - ansible: stable-2.12 |
244 |
| - # python: '3.6' |
245 |
| - # - ansible: stable-2.12 |
246 |
| - # python: '3.7' |
247 |
| - # - ansible: stable-2.12 |
248 |
| - # python: '3.8' |
249 |
| - # - ansible: stable-2.12 |
250 |
| - # python: '3.9' |
251 |
| - # - ansible: stable-2.12 |
252 |
| - # python: '3.10' |
| 199 | + # Add new versions announced in |
| 200 | + # https://github.com/ansible-collections/news-for-maintainers in a timely manner, |
| 201 | + # consider dropping testing against EOL versions and versions you don't support. |
253 | 202 | # ansible-core 2.13
|
254 | 203 | - ansible: stable-2.13
|
255 | 204 | python: '2.7'
|
|
0 commit comments