Separately control CPython versions in nightly CI #2242
Conversation
webknjaz
left a comment
There was a problem hiding this comment.
Alright.. This is fine short-term but what I really want is to push matrix definitions out of the reusable workflows so the reusable workflow would only have one job with one python/os/arch combo. This worked really well for reusable-tox.yml and we should work towards moving in the direction of the same style.
When this is done, we'd be able to control pairs of pip+python more granularly, on the calling side.
changelog.d/2226.misc.md
Outdated
| @@ -0,0 +1,2 @@ | |||
| Narrow the CPython versions tested in nightly CI runs and separate these from | |||
This sounds like a wonderful longer term solve. Let's queue it up as something to work on. I'm not a huge fan of the current solution, but I saw it as the shortest path towards healthier CI. (And this was listed for 7.5.1 so I wanted to choose either "put in a relatively easy solution" or "explicitly move it to 7.5.2".) |
c425ea0 to
31a60bb
Compare
The pip versions being tested are controlled via a JSON array passed as a string. Use the same mechanism to pass CPython versions to test. This allows PR builds to continue to test 3.8 (EOL) and 3.9 (EOL soon) while nightly builds will only run on 3.10+ .
31a60bb to
cd233dd
Compare
The pip versions being tested are controlled via a JSON array passed as
a string. Use the same mechanism to pass CPython versions to test.
This allows PR builds to continue to test 3.8 (EOL) and 3.9 (EOL soon)
while nightly builds will only run on 3.10+ .
Resolves #2226
Contributor checklist
Included tests for the changes.changelog.d/(seechangelog.d/README.mdfor instructions) or the PR text says "no changelog needed".Maintainer checklist
skip-changeloglabel.