# Jenkins CI is experiencing issues, consider re-push of branches for fresh runs

**URL:** <https://forum.djangoproject.com/t/jenkins-ci-is-experiencing-issues-consider-re-push-of-branches-for-fresh-runs/42371>\
**Category:** Django Internals\
**Created:** [August 13, 2025, 1:00am UTC](https://forum.djangoproject.com/t/jenkins-ci-is-experiencing-issues-consider-re-push-of-branches-for-fresh-runs/42371 "2025-08-13T01:00:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nessita](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/nessita/32/12194_2.png) [@nessita](https://forum.djangoproject.com/u/nessita)\
**Post date:** [August 13, 2025, 1:00am UTC](https://forum.djangoproject.com/t/jenkins-ci-is-experiencing-issues-consider-re-push-of-branches-for-fresh-runs/42371/1 "2025-08-13T01:00:35Z")

</div>

Hi everyone,

Just a quick heads-up: Jenkins CI has been experiencing multiple issues lately. Some are related to performance slowdowns, others to node availability, and a few are tied to specifics around Python versions (see [Fixed #36499 -- Adjusted utils\_tests.test\_html.TestUtilsHtml.test\_strip\_tags following Python's HTMLParser new behavior. by nessita · Pull Request #19639 · django/django · GitHub](https://github.com/django/django/pull/19639) if you are interested in details).

As a result, most (if not all) runs today have been failing for one reason or another. If you have pending pull requests with failed tests and those are not clearly related to your changes, please consider re-pushing them to trigger fresh CI runs once the issues have been addressed.

Thanks for your patience and understanding!