Hey everyone! I’ve been talking a lot with the Fellows recently about CI on pull requests, and how our current Jenkins-only setup is giving us some reliability, maintainability and performance challenges, resulting in extra friction and slowness in landing PRs, and reducing the number we can land each week.
As a result, in the short term we’re going to increase the number of test combinations we also run on GitHub Actions (we already run a few combinations there today, notably our Windows tests). We’re not going to get rid of the Jenkins ones right now - there’s a lot there that is hard to replace, especially Oracle - but we’d like to at least get to more platform, database and Python version coverage on GitHub Actions to see how it performs and hopefully let us merge more PRs, more smoothly.
This won’t result in any cost to the Django organization, so we don’t see any downside to just trying it out. Obviously, if it does prove to be consistently faster and more reliable, the discussion of moving testing to only GHA can be raised (as it has been before), but that’s not on the cards right now - that’s a bigger piece of work.
