# Expanding GitHub Actions testing for PRs

**URL:** <https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398>\
**Category:** Django Internals\
**Created:** [August 14, 2025, 3:50pm UTC](https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398 "2025-08-14T15:50:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrewgodwin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/andrewgodwin/32/2_2.png) [@andrewgodwin](https://forum.djangoproject.com/u/andrewgodwin)\
**Post date:** [August 14, 2025, 3:50pm UTC](https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398/1 "2025-08-14T15:50:04Z")

</div>

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](https://forum.djangoproject.com/t/improving-the-contribution-experience-with-github-actions/5964)), but that’s not on the cards right now - that’s a bigger piece of work.

---

<div class="post-metadata">

**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/carltongibson/32/267_2.png) [@carltongibson](https://forum.djangoproject.com/u/carltongibson)\
**Post date:** [August 14, 2025, 3:58pm UTC](https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398/2 "2025-08-14T15:58:35Z")

</div>

Great. Thanks Andrew. This looks like a sensible step 👍

---

<div class="post-metadata">

**Author:** ![CodenameTim](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/codenametim/32/31507_2.png) [@CodenameTim](https://forum.djangoproject.com/u/CodenameTim)\
**Post date:** [August 14, 2025, 4:28pm UTC](https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398/3 "2025-08-14T16:28:54Z")

</div>

Sounds good! Thanks for working on this.

---

<div class="post-metadata">

**Author:** ![frankwiles](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/frankwiles/32/386_2.png) [@frankwiles](https://forum.djangoproject.com/u/frankwiles)\
**Post date:** [August 18, 2025, 1:21pm UTC](https://forum.djangoproject.com/t/expanding-github-actions-testing-for-prs/42398/4 "2025-08-18T13:21:01Z")

</div>

I have no love for Jenkins (have lost far too many hours of my life to it) so yes please by all means!

While I get some things (Oracle notably) can’t be done with Github Actions. I’d be willing to help move those bits to something non-Jenkins as well. I’ve had really great experiences with [Concourse CI](https://concourse-ci.org) for example.