Skip to content
Signpost
DeprecatedInfrastructure

Jenkins pipelines

The previous CI system. Still running for pipelines that have not migrated, and switching off for good at the end of March 2027.

Being switched off on 31 March 2027

That is in 6 months. Anything still depending on this needs to move before then — to Self-hosted GitHub Actions runners.

Lifecycle

Next: retired on 31 March 2027, in 6 months.

  1. Proposed6 years ago
  2. In development6 years ago
  3. Generally available6 years ago
  4. Deprecated (current stage)8 months ago
  5. Retiredplanned, in 6 months

Detail

Why this is going away

Two CI systems means two sets of credentials, two sets of agents to patch and two places to look when a build breaks. The self-hosted Actions runners now cover everything Jenkins did for us.

What happens on 31 March 2027

The Jenkins controllers and agents are switched off and the hosts are reclaimed. Build history will be exported to object storage and kept for two years; there will be no running UI to browse it.

What we need from you

Migrate before the date, or tell us your pipeline can be deleted. Both are fine answers — silence is not.

Updates

Action required

38 pipelines still to migrate before the March 2027 shutdown

We will contact owning teams individually from October. If your pipeline is on the list and you think it should simply be deleted, tell us — that is often the right answer for pipelines nobody has run this year.

Action required

Jenkins is deprecated — move to GitHub Actions runners

No new pipelines will be created on Jenkins. Existing ones keep running until 31 March 2027, after which the servers are switched off.