Does anyone recall why we don't use GitHub Actions...
# developmenth
happy-kitchen-89482
08/09/2022, 1:33 PMDoes anyone recall why we don't use GitHub Actions' matrix strategy to build wheels for the different pythons orthogonally? Instead our jobs have a "primary Python" and then jump through hoops to expose the other Pythons on the path, and then build wheels for each python sequentially. We do invoke the matrix strategy, but we only pass it the "primary Python" as a singleton...
happy-kitchen-89482
08/09/2022, 1:34 PMGenerally our CI scripts are pretty idiosyncratic and not as composable as we would like.
e
enough-analyst-54434
08/09/2022, 1:38 PMProbably the CentoOS container? Looks like we use a manylinux image now, but is that a matrix road-bump? Linux uses a container, mac does not?
h
hundreds-father-404
08/09/2022, 1:38 PMProbably because they were ported very very incrementally from Travis CI, and our generate script from bash to Python
h
happy-kitchen-89482
08/09/2022, 2:13 PMWe do use the matrix for the daily extended testing job (that fails and no one looks at, but that's another issue...) so it probably could work
👍 1
happy-kitchen-89482
08/09/2022, 2:13 PMOK, just checking that there's no gotcha here, if I decide to clean it up
happy-kitchen-89482
08/09/2022, 2:14 PMit would be great if everything truly was a matrix - select OS version and python version and what you want to do on that platform (run tests, build wheels, etc) and the right config pops out 🙂
happy-kitchen-89482
08/09/2022, 2:14 PMThat said, since we're generating the config anyway, we probably don't need the matrix stuff at all
happy-kitchen-89482
08/09/2022, 2:14 PMWe make our own matrix
happy-kitchen-89482
08/09/2022, 2:14 PMinsert The Matrix meme here
b
bitter-ability-32190
08/09/2022, 2:50 PMShifting the matrix responsibility onto GitHub does mean less hoops on our end, simpler CI config, and easier contributions 🙂
I try not to touch CI much because I'm afraid 😛