<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jenkins Status Page</title><link>https://status.jenkins.io/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>Thu, 16 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://status.jenkins.io/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] update center issue</title><link>https://status.jenkins.io/issues/2026-04-16-update-center-issues/</link><pubDate>Thu, 16 Apr 2026 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-04-16-update-center-issues/</guid><category>2026-04-16T10:05:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The issue was relarted to CNI driver of publick8s cluster, resolved after recycling its nodes.&lt;/p&gt;
&lt;p&gt;Update Center is back to normal.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;updates.jenkins.io is returning random HTTP/502 errors, plugin updates are stuck.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re working on it, expect an LDAP restart.&lt;/p&gt;</description></item><item><title>Problems on plugins.jenkins.io: search and changelogs</title><link>https://status.jenkins.io/issues/2026-04-14-plugin-site-search-unavailable/</link><pubDate>Tue, 14 Apr 2026 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-04-14-plugin-site-search-unavailable/</guid><category/><description>&lt;p&gt;[Update]
We&amp;rsquo;ve disabled the search temporarily to ensure plugins.jenkins.io stays up-to-date, fixing the changelog content problem.&lt;/p&gt;
&lt;p&gt;[Update]&lt;/p&gt;
&lt;p&gt;Plugins changelogs seems broken since the 13 April 2026 and only reports old versions of plugins while new versions are available.&lt;/p&gt;
&lt;p&gt;[Initial message]
Plugin search on &lt;a href="https://plugins.jenkins.io/"&gt;plugins.jenkins.io&lt;/a&gt; is currently not returning results. Individual plugin pages are still accessible via direct URL (e.g. &lt;a href="https://plugins.jenkins.io/git/)"&gt;https://plugins.jenkins.io/git/)&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The issue appears to be related to Algolia search quota exhaustion, likely caused by increased automated/LLM scraping of the search facility.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/5066"&gt;https://github.com/jenkins-infra/helpdesk/issues/5066&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2026-03-18-ci-maintenance-sec-advisory/</link><pubDate>Wed, 18 Mar 2026 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-03-18-ci-maintenance-sec-advisory/</guid><category>2026-03-18T13:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest plugins and with latest LTS 2.541.3 Core version.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Wednesday March 18 2026, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as part of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/Zkir_LMxL7c"&gt;https://groups.google.com/g/jenkinsci-advisories/c/Zkir_LMxL7c&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2026-03-10-trusted-cert-cijenkins-maintenances/</link><pubDate>Tue, 10 Mar 2026 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-03-10-trusted-cert-cijenkins-maintenances/</guid><category>2026-03-10T11:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Operation completed successfully&lt;/p&gt;
&lt;p&gt;[Initial Message]
Tuesday March 10 2026, starting at 09:00 UTC, the Jenkins controllers and agents on trusted.ci.jenkins.io, cert.ci.jenkin.io, and ci.jenkins.io will be upgraded to use JDK25 at runtime instead of JDK21.&lt;/p&gt;
&lt;p&gt;This operation will require controller restarts and agent reconnections. A short service disruption is expected during the maintenance window.&lt;/p&gt;
&lt;p&gt;See more details at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4941"&gt;https://github.com/jenkins-infra/helpdesk/issues/4941&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on release.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2026-03-02-releaseci-maintenances/</link><pubDate>Mon, 02 Mar 2026 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-03-02-releaseci-maintenances/</guid><category>2026-03-02T10:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Operation completed successfully&lt;/p&gt;
&lt;p&gt;[Initial Message]
Friday 2026, starting at 09:00 UTC, the Jenkins controllers and agents on release.ci.jenkins.io will be upgraded to use JDK25 at runtime instead of JDK21.&lt;/p&gt;
&lt;p&gt;This operation will require controller restarts and agent reconnections. A short service disruption is expected during the maintenance window.&lt;/p&gt;
&lt;p&gt;See more details at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4941"&gt;https://github.com/jenkins-infra/helpdesk/issues/4941&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on weekly.ci.jenkins.io and infra.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2026-02-27-infraci-and-weeklyci-maintenances/</link><pubDate>Fri, 27 Feb 2026 09:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-02-27-infraci-and-weeklyci-maintenances/</guid><category>2026-02-27T10:00:00-00:00</category><description>&lt;p&gt;[Initial Message]
Friday February 27 2026, starting at 09:30 UTC, the Jenkins controllers and agents on weekly.ci.jenkins.io and infra.ci.jenkins.io will be upgraded to use JDK25 at runtime instead of JDK21.&lt;/p&gt;
&lt;p&gt;This operation will require controller restarts and agent reconnections. A short service disruption is expected during the maintenance window.&lt;/p&gt;
&lt;p&gt;See more details at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4941"&gt;https://github.com/jenkins-infra/helpdesk/issues/4941&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] jenkins.io website outage</title><link>https://status.jenkins.io/issues/2026-02-03-jenkins.io-outage/</link><pubDate>Mon, 02 Feb 2026 19:40:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-02-03-jenkins.io-outage/</guid><category>2026-02-03T13:25:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;All services are back online, more details will be posted in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4978"&gt;https://github.com/jenkins-infra/helpdesk/issues/4978&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
Jenkins website and some other services are down, currently investigating.&lt;/p&gt;
&lt;p&gt;See details and updates at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4978"&gt;https://github.com/jenkins-infra/helpdesk/issues/4978&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io enforced login and users cleanup</title><link>https://status.jenkins.io/issues/2026-01-28-ci.jenkins.io-users-cleanup-and-enforced-login/</link><pubDate>Wed, 28 Jan 2026 18:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-01-28-ci.jenkins.io-users-cleanup-and-enforced-login/</guid><category>2026-01-28T18:30:00-00:00</category><description>&lt;p&gt;[Initial Message]
On Wednesday 28 January 2026 at 18h15 UTC, ci.jenkins.io will require authentication with a Jenkins LDAP account to allow reading pages.&lt;/p&gt;
&lt;p&gt;As part of this change, the users database will be wiped out, effectively removing all API tokens and personal preferences.
Direct consequence: incrementals.jenkins.io won&amp;rsquo;t be able to deliver new incremental releases until a new API token is generated.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center slow due to CloudFlare outage</title><link>https://status.jenkins.io/issues/2026-01-20-uc-cloudflare-outage/</link><pubDate>Tue, 20 Jan 2026 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-01-20-uc-cloudflare-outage/</guid><category>2026-01-20T09:30:00-00:00</category><description>&lt;p&gt;[Final Message]
CloudFlare maintenance is finished: we&amp;rsquo;ve enabled the East America mirror as it is now responding as expected.&lt;/p&gt;
&lt;p&gt;[Initial Message]
CloudFlare is performing a maintenance (&lt;a href="https://www.cloudflarestatus.com/incidents/t1sp3rqqpxcj"&gt;https://www.cloudflarestatus.com/incidents/y5xbgk3fh95y&lt;/a&gt;) with re-routed traffic.
Since 07:30 UTC, our monitoring detected a lot of timeouts for the Update Center requests targeted at our East US mirror
due to the re-routing latency.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve disabled the East US mirror in favor of West europe or archives.jenkins.io at 08:00 UTC for now.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io disruption</title><link>https://status.jenkins.io/issues/2026-01-13-ci.jenkins.io-oom/</link><pubDate>Tue, 13 Jan 2026 05:10:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2026-01-13-ci.jenkins.io-oom/</guid><category>2026-01-13T17:40:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is back to a normal response time. The AI crawler has stopped sending requests.
We had to restart the controller once per hour to sustain the high rate of requests.&lt;/p&gt;
&lt;p&gt;[Initial message] &amp;ndash;&amp;gt;
ci.jenkins.io is failing with Out Of Memory errors, we&amp;rsquo;ve restarted it.
We don&amp;rsquo;t know yet the exact cause but we&amp;rsquo;re suspecting AI crawlers.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of pkg.origin.jenkins.io service from AWS to Azure</title><link>https://status.jenkins.io/issues/2025-12-19-pkg-migration-to-azure/</link><pubDate>Fri, 19 Dec 2025 09:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-19-pkg-migration-to-azure/</guid><category>2025-12-20T10:00:00-00:00</category><description>&lt;p&gt;On December 19th at 09h30am UTC, we&amp;rsquo;ll migrate the service &lt;code&gt;pkg.origin.jenkins.io&lt;/code&gt; from AWS to Azure.&lt;/p&gt;
&lt;p&gt;This service is the source of data for the Fastly CDN service &lt;code&gt;pkg.jenkins.io&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We expect a slight slow down for users installing Jenkins Debian/RPM packages (or browsing the pages of this service).&lt;/li&gt;
&lt;li&gt;In case of unexpected error, installation of Jenkins Debian/RPM packages (or browsing the pages of this service) will be disrupted until the operation is finished.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See more details at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3705"&gt;https://github.com/jenkins-infra/helpdesk/issues/3705&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.33.5</title><link>https://status.jenkins.io/issues/2025-12-15-maintenance-azure-publick8s-1-33/</link><pubDate>Mon, 15 Dec 2025 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-15-maintenance-azure-publick8s-1-33/</guid><category>2025-12-15T09:15:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Monday 15 December 2025 at 08:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.33.5. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;issue-redirect.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548729217"&gt;https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548729217&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [privatek8s cluster] Azure privatek8s Upgrade to Kubernetes 1.33.5</title><link>https://status.jenkins.io/issues/2025-12-11-maintenance-azure-privatek8s-1-33/</link><pubDate>Fri, 12 Dec 2025 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-11-maintenance-azure-privatek8s-1-33/</guid><category>2025-12-12T10:30:00-00:00</category><description>&lt;p&gt;[Final message]
Upgrade completed without any issue. We&amp;rsquo;ve done it today only as yesterday GitHub was too unstable to perform it without hitting issues when pulling terraform providers or helm repositories.&lt;/p&gt;
&lt;p&gt;[Initial message]
Friday 12 December 2025 at 09:00 UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;privatek8s&lt;/code&gt; to Kubernetes 1.33.5. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;Expect multiple restarts and downtimes for the infra.ci.jenkins.io and release.ci.jenkins.io controllers along with the github-comment-ops bots.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548723638"&gt;https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548723638&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2025-12-10-ci-maintenance-sec-advisory/</link><pubDate>Wed, 10 Dec 2025 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-10-ci-maintenance-sec-advisory/</guid><category>2025-12-10T14:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest plugins and with latest LTS 2.528.3 Core version.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday December 10 2025, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as part of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/PN3lF_72LfU"&gt;https://groups.google.com/g/jenkinsci-advisories/c/PN3lF_72LfU&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [ci.jenkins.io container agents] AWS EKS Upgrade to Kubernetes 1.33.5</title><link>https://status.jenkins.io/issues/2025-12-04-maintenance-aws-cijioagents2-1-33/</link><pubDate>Thu, 04 Dec 2025 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-04-maintenance-aws-cijioagents2-1-33/</guid><category>2025-12-04T14:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The upgrade went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 4 December 2025, at 12:00 UTC, we&amp;rsquo;ll upgrade the EKS(AWS) cluster hosting ci.jenkins.io&amp;rsquo;s container agents and Artifact Caching proxy to Kubernetes 1.33.5&lt;/p&gt;
&lt;p&gt;All agents using &lt;code&gt;jnlp-linux-*&lt;/code&gt; or &lt;code&gt;jnlp-bom&lt;/code&gt; labels, or pipelines with the &lt;code&gt;buildPlugin()&lt;/code&gt; function with &lt;code&gt;useContainer: true&lt;/code&gt; will be queued until the end of the operation.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3607329009"&gt;https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3607329009&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Jenkins core issues are migrating from Jira to GitHub</title><link>https://status.jenkins.io/issues/2025-11-24-jira-core-migrate-to-github/</link><pubDate>Mon, 24 Nov 2025 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-11-24-jira-core-migrate-to-github/</guid><category>2025-12-08T08:00:00-00:00</category><description>&lt;p&gt;All Jira issues for Jenkins core are currently being migrated to GitHub.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkinsci/jenkins/issues/11301"&gt;https://github.com/jenkinsci/jenkins/issues/11301&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] CloudFlare outage</title><link>https://status.jenkins.io/issues/2025-11-18-cloudflare-outage/</link><pubDate>Tue, 18 Nov 2025 11:48:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-11-18-cloudflare-outage/</guid><category>2025-11-18T19:30:00-00:00</category><description>&lt;p&gt;Final message:
CloudFlare incident has been resolved:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency across the network.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Initial message:
CloudFlare is down: &lt;a href="https://www.cloudflarestatus.com/incidents/8gmgl950y3h7"&gt;https://www.cloudflarestatus.com/incidents/8gmgl950y3h7&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This impacts the Update Center, and element channels like #jenkins-infra&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll keep this status updated.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) LTS upgrade maintenance window</title><link>https://status.jenkins.io/issues/2025-11-13-jira-lts-upgrade/</link><pubDate>Thu, 13 Nov 2025 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-11-13-jira-lts-upgrade/</guid><category>2025-11-13T23:38:00-00:00</category><description>&lt;p&gt;The Jira instance at &lt;a href="https://issues.jenkins.io"&gt;https://issues.jenkins.io&lt;/a&gt;, managed by the Linux Foundation team, will be down for up to 8 hours beginning at 16:00 UTC on Thursday November 13, 2025 to perform an LTS upgrade from 9.x to 10.x.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4644"&gt;https://github.com/jenkins-infra/helpdesk/issues/4644&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Azure outage on the '*.ci.jenkins.io' private controllers</title><link>https://status.jenkins.io/issues/2025-10-29-azure-outage/</link><pubDate>Wed, 29 Oct 2025 15:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-29-azure-outage/</guid><category>2025-10-30T00:05:00-00:00</category><description>&lt;p&gt;[Final Message]
The outage seems has been resolved at 00:05am on the 30 October.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Azure is facing a global outage (Tracking ID: YKYN-BWZ at &lt;a href="https://azure.status.microsoft/en-us/status/history/"&gt;https://azure.status.microsoft/en-us/status/history/&lt;/a&gt;) which prevents access to the Azure Portal and to the Azure Identity Management API.&lt;/p&gt;
&lt;p&gt;It means that our private controllers might be unable to spin up new VM agents: we expect delays in&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The publication of our websites (both previews and production)&lt;/li&gt;
&lt;li&gt;Jobs running in private controllers&lt;/li&gt;
&lt;li&gt;Execution of infrastructure related tasks (Terraform and Kubernetes jobs)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Jobs will be queued and eventually aborted due to timeouts.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on incrementals.jenkins.io</title><link>https://status.jenkins.io/issues/2025-10-27-incrementals-outage/</link><pubDate>Mon, 27 Oct 2025 07:56:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-27-incrementals-outage/</guid><category>2025-10-27T14:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The error has been identified and fixed (token regeneration). Service is back to normal.&lt;/p&gt;
&lt;p&gt;[Initial Message]
We are encountering an outage on incrementals.jenkins.io, currently investigating.&lt;/p&gt;
&lt;p&gt;More info at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4852"&gt;https://github.com/jenkins-infra/helpdesk/issues/4852&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on incrementals.jenkins.io</title><link>https://status.jenkins.io/issues/2025-10-16-incrementals-outage/</link><pubDate>Wed, 15 Oct 2025 15:41:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-16-incrementals-outage/</guid><category>2025-10-16T16:23:00-00:00</category><description>&lt;p&gt;[Final Message]
The error has been identified and a fix (token rotation) has immediately been applied. Service is back to normal.&lt;/p&gt;
&lt;p&gt;[Initial Message]
We are encountering an outage on incrementals.jenkins.io, currently investigating.&lt;/p&gt;
&lt;p&gt;More info at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4840"&gt;https://github.com/jenkins-infra/helpdesk/issues/4840&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Outage on get.jenkins.io and updates.jenkins.io</title><link>https://status.jenkins.io/issues/2025-10-09-azure-outage/</link><pubDate>Thu, 09 Oct 2025 07:08:20 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-09-azure-outage/</guid><category>2025-10-09T10:08:20-00:00</category><description>&lt;p&gt;[Final Message]
The outage seems resolved &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4827"&gt;https://github.com/jenkins-infra/helpdesk/issues/4827&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial Message]
we are encountering an outage on get.jenkins.io and updates.jenkins.io our publick8s cluster. We are seeing problems that azure doesn&amp;rsquo;t acknowledge, probably related to an Azure outage.&lt;/p&gt;
&lt;p&gt;see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4827"&gt;https://github.com/jenkins-infra/helpdesk/issues/4827&lt;/a&gt; for information&lt;/p&gt;</description></item><item><title>[Resolved] Outage on get.jenkins.io and updates.jenkins.io</title><link>https://status.jenkins.io/issues/2025-10-07-get.jenkins.io-outage/</link><pubDate>Tue, 07 Oct 2025 07:03:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-07-get.jenkins.io-outage/</guid><category>2025-10-07T14:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The outage seems resolved &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4827"&gt;https://github.com/jenkins-infra/helpdesk/issues/4827&lt;/a&gt; .
We did a refresh of the 3 nodes of publick8s but were impacted with an azure outage that is not public yet.&lt;/p&gt;
&lt;p&gt;[Initial Message]
We are encountering an outage on get.jenkins.io, currently investigating.
The same problem is visible on updates.jenkins.io.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of usage.jenkins.io to Digital Ocean</title><link>https://status.jenkins.io/issues/2025-10-02-usage-migration/</link><pubDate>Thu, 02 Oct 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-10-02-usage-migration/</guid><category>2025-10-02T08:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday October 02 2025, &lt;code&gt;usage.jenkins.io&lt;/code&gt; VM will be migrated from AWS to Digital Ocean as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/1626"&gt;https://github.com/jenkins-infra/helpdesk/issues/1626&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We expect between 30mn and 2h of downtime starting at 08:00 AM UTC.&lt;/p&gt;</description></item><item><title>[Resolved] Azure cluster publick8s migrated to a new location and upgraded to Kubernetes 1.32</title><link>https://status.jenkins.io/issues/2025-09-25-azure-publick8s-1-32-adn-migration/</link><pubDate>Thu, 25 Sep 2025 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-09-25-azure-publick8s-1-32-adn-migration/</guid><category>2025-09-26T09:30:00-00:00</category><description>&lt;p&gt;[Final Message]
Outage finished on Friday 26 September 2025 at 09:35am UTC and post mortem published: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Friday 26 September 2025 at 09:35am UTC: ongoing production outage on the cluster (unexpected side effect of the migration): &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Migration was finished on Thursday 25 September 2025 at 03:30PM UTC. See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339"&gt;https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 25 September 2025, starting at 11:30AM UTC, we&amp;rsquo;ll perform a migration + upgrade of the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to a new location and to Kubernetes 1.32.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4617"&gt;https://github.com/jenkins-infra/helpdesk/issues/4617&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io authentication required</title><link>https://status.jenkins.io/issues/2025-09-19-ci.jenkins.io-auth-brownout/</link><pubDate>Fri, 19 Sep 2025 12:44:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-09-19-ci.jenkins.io-auth-brownout/</guid><category>2025-09-19T14:20:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is now up and running, the brownout is done, we will have to work around permission for the next brownout.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4768"&gt;https://github.com/jenkins-infra/helpdesk/issues/4768&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
A large set of unhelpful requests are overloading ci.jenkins.io.
We are in a brownout.
We are testing that disallowing anonymous access resolves the performance issue.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4768"&gt;https://github.com/jenkins-infra/helpdesk/issues/4768&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2025-09-17-ci-maintenance-sec-advisory/</link><pubDate>Wed, 17 Sep 2025 09:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-09-17-ci-maintenance-sec-advisory/</guid><category>2025-09-17T10:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest plugins and with latest LTS 2.516.3 Core version.
Weekly.ci is running with latest weekly 2.528 Core version&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday September 17 2025, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as part of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/rOpnrQxJWEY"&gt;https://groups.google.com/g/jenkinsci-advisories/c/rOpnrQxJWEY&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Enforced HTTPS for Update Center</title><link>https://status.jenkins.io/issues/2025-08-06-uc-enforce-https/</link><pubDate>Wed, 06 Aug 2025 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-08-06-uc-enforce-https/</guid><category>2025-08-06T09:30:00-00:00</category><description>&lt;p&gt;Wednesday 06 August 2025 at 07:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will be upgraded to enforced HTTPS as described in &lt;a href="https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/"&gt;https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The operation should take from 5 to 30 minutes (depends on the Azure Cloud ability to spin up resources on demand).&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.
Eventually, some requests may time out during the deployment of the new settings.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4758"&gt;https://github.com/jenkins-infra/helpdesk/issues/4758&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Expired TLS certificate on issues.jenkins.io</title><link>https://status.jenkins.io/issues/2025-08-02-jira-tls-expired/</link><pubDate>Sat, 02 Aug 2025 22:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-08-02-jira-tls-expired/</guid><category>2025-08-03T07:30:00-00:00</category><description>&lt;p&gt;[Final Message]
Linux foundation shared with Jenkins Infra team the required elements (DNS ACME challenge value) to allow automatic renewal of the TLS certificate.
The certificate has been finally renewed at 07h30(am) UTC.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The JIRA service at issues.jenkins.io (issues.jenkins-ci.org) is unavailable due to an expired TLS certificate.&lt;/p&gt;
&lt;p&gt;The Jenkins infrastructure is working with the Linux Foundation team (whom manage the JIRA service) to solve this issue.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4757"&gt;https://github.com/jenkins-infra/helpdesk/issues/4757&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] infra.ci.jenkins.io down</title><link>https://status.jenkins.io/issues/2025-07-29-infra.ci-down/</link><pubDate>Mon, 28 Jul 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-07-29-infra.ci-down/</guid><category>2025-07-28T14:45:00-00:00</category><description>&lt;p&gt;[Final message]
infra.ci is back to business after a migration to another cluster which allowed to find the root cause and fix it.&lt;/p&gt;
&lt;p&gt;[Initial message]
The infra.ci.jenkins.io (private) Jenkins controller is down with error related to cloud storage.
We are currently analyzing the issue and fixing it.&lt;/p&gt;
&lt;p&gt;All website previews in pull requests, along with deployment of plugins.jenkins.io, docs.jenkins.io and stats.jenkins.io are down.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4753"&gt;https://github.com/jenkins-infra/helpdesk/issues/4753&lt;/a&gt; for details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2025-07-09-ci-maintenance-sec-advisory/</link><pubDate>Wed, 09 Jul 2025 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-07-09-ci-maintenance-sec-advisory/</guid><category>2025-07-09T13:30:00-00:00</category><description>&lt;p&gt;Wednesday July 07 2025, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as part of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/doaM4i0Qf6o"&gt;https://groups.google.com/g/jenkinsci-advisories/c/doaM4i0Qf6o&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of ci.jenkins.io to AWS</title><link>https://status.jenkins.io/issues/2025-07-07-ci-migration/</link><pubDate>Mon, 07 Jul 2025 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-07-07-ci-migration/</guid><category>2025-07-07T08:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Monday July 07 2025, &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be migrated from Azure to AWS as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4688"&gt;https://github.com/jenkins-infra/helpdesk/issues/4688&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We expect between 2h to 4h of downtime starting at 07:00 AM UTC.&lt;/p&gt;</description></item><item><title>[Resolved] jdk21 upgrade for runtime controllers and agents</title><link>https://status.jenkins.io/issues/2025-05-22-jdk21-runtime-controllers-agents-maintenances/</link><pubDate>Thu, 22 May 2025 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-05-22-jdk21-runtime-controllers-agents-maintenances/</guid><category>2025-05-22T16:00:00-00:00</category><description>&lt;p&gt;[Final Message]
migration went well, no impact on production.
few fixes to apply with &lt;a href="https://github.com/jenkins-infra/jenkins-infra/pull/4143"&gt;https://github.com/jenkins-infra/jenkins-infra/pull/4143&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday May 22 2025, starting at &lt;del&gt;17:00&lt;/del&gt; 13:00 UTC, all our controllers and there agents will be upgraded to use JDK21 as runtime version instead of JDK17.&lt;/p&gt;
&lt;p&gt;This operation expects 1 or 2 restarts per controller &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4121#issuecomment-2890355054"&gt;https://github.com/jenkins-infra/helpdesk/issues/4121#issuecomment-2890355054&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Uplink service is unavailable</title><link>https://status.jenkins.io/issues/2025-05-20-uplink-outage/</link><pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-05-20-uplink-outage/</guid><category>2025-05-23T13:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The service is back with an empty database. Telemtry is now collected properly.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The service uplink is unavailable due to database issue.
Any tentative to log-in ends up in &amp;ldquo;Internal Server Error&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4667"&gt;https://github.com/jenkins-infra/helpdesk/issues/4667&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] LDAP offline for reindex</title><link>https://status.jenkins.io/issues/2025-05-06-ldap-reindex/</link><pubDate>Tue, 06 May 2025 17:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-05-06-ldap-reindex/</guid><category>2025-05-06T18:30:00-00:00</category><description>&lt;p&gt;The LDAP service requires a reindex which needs LDAP server to be offline.
Starting the operation at 17h50 UTC, finished at 18h30 UTC with success.&lt;/p&gt;</description></item><item><title>[Resolved] [privatek8s cluster] Migrate to another Azure subscription</title><link>https://status.jenkins.io/issues/2025-04-29-migration-azure-privatek8s/</link><pubDate>Tue, 29 Apr 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-29-migration-azure-privatek8s/</guid><category>2025-04-29T16:00:00-00:00</category><description>&lt;p&gt;Tuesday 29 April 2025, at 08:00am UTC, the cluster &lt;code&gt;privatek8s&lt;/code&gt; will be migrated between Azure subscriptions.&lt;/p&gt;
&lt;p&gt;Expect a full downtime of infra.ci.jenkins.io and release.ci.jenkins.io from 2 hours up to 8 hours.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4250"&gt;https://github.com/jenkins-infra/helpdesk/issues/4250&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.31.6</title><link>https://status.jenkins.io/issues/2025-04-24-maintenance-azure-publick8s-1-31/</link><pubDate>Thu, 24 Apr 2025 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-24-maintenance-azure-publick8s-1-31/</guid><category>2025-04-24T8:20:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 24 April 2025, at 07:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.31.6. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;⚠️ Last Kubernetes upgrade (to 1.30) we saw an outage on update-center (updates.jenkins.io) for a few seconds !&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674545933"&gt;https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674545933&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [privatek8s cluster] Azure privatek8s Upgrade to Kubernetes 1.31.6</title><link>https://status.jenkins.io/issues/2025-04-23-maintenance-azure-privatek8s-1-31/</link><pubDate>Wed, 23 Apr 2025 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-23-maintenance-azure-privatek8s-1-31/</guid><category>2025-04-23T13:00:00-00:00</category><description>&lt;p&gt;Wednesday 23 April 2025, at 12:30 UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;privatek8s&lt;/code&gt; to Kubernetes 1.31.6. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;Expect multiple restarts and downtimes for the infra.ci.jenkins.io and release.ci.jenkins.io controllers along with the github-comment-ops bots.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674551720"&gt;https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674551720&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of ci.jenkins.io to Azure</title><link>https://status.jenkins.io/issues/2025-04-09-ci-migration-to-azure/</link><pubDate>Wed, 09 Apr 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-09-ci-migration-to-azure/</guid><category>2025-04-09T09:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Wednesday April 09 2025, at 08:00 AM UTC, the Jenkins Infra team will migrate the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller from AWS to Azure as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4620"&gt;https://github.com/jenkins-infra/helpdesk/issues/4620&lt;/a&gt;.
We expect a downtime of 2 hours.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2025-04-02-ci-maintenance-sec-advisory/</link><pubDate>Wed, 02 Apr 2025 14:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-02-ci-maintenance-sec-advisory/</guid><category>2025-04-02T15:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest LTS 2.479.3 Core version.
The weekly.ci.jenkins.io controller is running with latest weekly 2.504 Core version.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday April 02 2025, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; and &lt;code&gt;weekly.ci.jenkins.io&lt;/code&gt; controllers will be put offline and updated as a result of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/gjEkmc02cU0"&gt;https://groups.google.com/g/jenkinsci-advisories/c/gjEkmc02cU0&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2025-03-05-ci-maintenance-sec-advisory/</link><pubDate>Wed, 05 Mar 2025 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-03-05-ci-maintenance-sec-advisory/</guid><category>2025-03-05T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest LTS 2.479.2 Core version.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday March 05 2025, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as a result of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/7ZO66tLSKa8"&gt;https://groups.google.com/g/jenkinsci-advisories/c/7ZO66tLSKa8&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.30.7</title><link>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-publick8s-1-30/</link><pubDate>Thu, 20 Feb 2025 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-publick8s-1-30/</guid><category>2025-02-20T14:10:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well but we saw an outage on update center for about 2 to 3 mn
we will analyse further the logs to try to understand were it&amp;rsquo;s coming from&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thurday 20 February 2025, at 01:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.30.7. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2663553626"&gt;https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2663553626&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [privatek8s cluster] Azure privatek8s Upgrade to Kubernetes 1.30.7</title><link>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-privatek8s-1-30/</link><pubDate>Thu, 20 Feb 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-privatek8s-1-30/</guid><category>2025-02-20T08:35:00-00:00</category><description>&lt;p&gt;[Final Message]
Upgrade went well. Had to wait for the infra.ci mounting volume : &lt;code&gt;Warning FailedAttachVolume 5m35s attachdetach-controller Multi-Attach error for volume &amp;quot;jenkins-infra-pv&amp;quot; Volume is already exclusively attached to one node and can't be attached to another&lt;/code&gt;
but seems faster than before.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thurday 20 February 2025, at 08:00 UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;privatek8s&lt;/code&gt; to Kubernetes 1.30.7. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;Expect multiple restarts and downtimes for the infra.ci.jenkins.io and release.ci.jenkins.io controllers along with the github-comment-ops bots.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2668175339"&gt;https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2668175339&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [ci.jenkins.io container agents] AWS EKS Upgrade to Kubernetes 1.30.9</title><link>https://status.jenkins.io/issues/2025-02-19-maintenance-aws-cijioagents2-1-30/</link><pubDate>Wed, 19 Feb 2025 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-19-maintenance-aws-cijioagents2-1-30/</guid><category>2025-02-19T09:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The upgrade went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Wednesday 19 February 2025, at 08:00 UTC, we&amp;rsquo;ll upgrade the EKS(AWS) cluster hosting ci.jenkins.io&amp;rsquo;s container agents and Artifact Caching proxy to Kubernetes 1.30.9&lt;/p&gt;
&lt;p&gt;All agents using &lt;code&gt;jnlp-linux-*&lt;/code&gt; or &lt;code&gt;jnlp-bom&lt;/code&gt; labels, or pipelines with the &lt;code&gt;buildPlugin()&lt;/code&gt; function with &lt;code&gt;useContainer: true&lt;/code&gt; will be queued until the end of the operation.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2666362598"&gt;https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2666362598&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2025-02-14-aws.ci.jenkins.io-outage/</link><pubDate>Fri, 14 Feb 2025 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-14-aws.ci.jenkins.io-outage/</guid><category>2025-02-14T13:30:00-00:00</category><description>&lt;p&gt;Following ci migration to aws, we are encountering an outage on ci.jenkins.io, currently investigating&lt;/p&gt;</description></item><item><title>[Resolved] Migration of ci.jenkins.io to AWS</title><link>https://status.jenkins.io/issues/2025-02-13-ci-migration/</link><pubDate>Thu, 13 Feb 2025 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-13-ci-migration/</guid><category>2025-02-13T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well, all tests are green.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;Now, Thursday February 13 2025, we will start the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller migration to aws as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4315#issuecomment-2655944334"&gt;https://github.com/jenkins-infra/helpdesk/issues/4315#issuecomment-2655944334&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We expect at least 4h of downtime starting at 09:00 AM UTC&lt;/p&gt;</description></item><item><title>[Resolved] ldap outage</title><link>https://status.jenkins.io/issues/2025-02-06-ldap-outage/</link><pubDate>Fri, 07 Feb 2025 01:40:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-06-ldap-outage/</guid><category>2025-02-07T08:40:00-00:00</category><description>&lt;p&gt;[Final Message]
The issue was identified to be an undocumented missing permission between Kubernetes and the LDAP data disk during Kubernetes Node upgrade.
It has been fixed and persisted.&lt;/p&gt;
&lt;p&gt;[Initial Message]
ldap service is down so no authentification for Jira, Artifactory, or Jenkins controllers.
&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4531"&gt;Help desk 4531&lt;/a&gt; is tracking progress on the issue.&lt;/p&gt;</description></item><item><title>[Resolved] Azure Outage / ci.jenkins.io Windows Container Agents</title><link>https://status.jenkins.io/issues/2025-01-08-ci.jenkins.io-azure-outage/</link><pubDate>Wed, 08 Jan 2025 22:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-01-08-ci.jenkins.io-azure-outage/</guid><category>2025-01-30T17:30:00-00:00</category><description>&lt;p&gt;[Final Message]
Outage is finished: back to normal&lt;/p&gt;
&lt;p&gt;[Update]
still in outage at this date an time 14 january 2025 1:45PM&lt;/p&gt;
&lt;p&gt;[Update]
&lt;!-- raw HTML omitted --&gt;The Azure outage finished the 04:30 UTC on 11 Jan 2025 &lt;!-- raw HTML omitted --&gt; (as per &lt;a href="https://azure.status.microsoft/en-us/status/history/"&gt;https://azure.status.microsoft/en-us/status/history/&lt;/a&gt;, Tracking ID: &lt;code&gt;PLP3-1W8&lt;/code&gt;).
Windows (container) builds are now flowing on ci.jenkins.io.&lt;/p&gt;
&lt;p&gt;[Initial Message]
A network Azure outage in the region US East 2 started at 22:00 UTC the 8 January 2025 impacts the Jenkins infrastructure.&lt;/p&gt;
&lt;p&gt;Most notably, Windows container agents (using Azure Container Instances) are not starting, associated builds are stuck in the queue.&lt;/p&gt;
&lt;p&gt;Short term: users can set &lt;code&gt;useContainerAgent&lt;/code&gt; to &lt;code&gt;false&lt;/code&gt; in their &lt;code&gt;buildPlugin()&lt;/code&gt; pipeline library function to force usage of VMs instead of containers.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4490"&gt;https://github.com/jenkins-infra/helpdesk/issues/4490&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2024-12-22-artifactory-outage/</link><pubDate>Sun, 22 Dec 2024 12:40:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-12-22-artifactory-outage/</guid><category>2024-12-22T17:30:00-00:00</category><description>&lt;p&gt;The JFrog Artifactory service at &amp;lt;repo.jenkins-ci.org&amp;gt; is facing an outage on JFrog&amp;rsquo;s side.
It only answers HTTP/500 or HTTP/504 errors when trying to access it.&lt;/p&gt;
&lt;p&gt;Maven builds are also affected (both locally and on ci.jenkins.io).&lt;/p&gt;</description></item><item><title>[Resolved] AKS cluster upgrade to 1.29.10 (patch)</title><link>https://status.jenkins.io/issues/2024-12-18-maintenance-aks-1.29.10/</link><pubDate>Wed, 18 Dec 2024 09:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-12-18-maintenance-aks-1.29.10/</guid><category>2024-12-18T14:00:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re performing AKS cluster upgrade from 1.29.7 to 1.29.10 the 18 December 2024, starting at 09:45 UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) upgrade and restart</title><link>https://status.jenkins.io/issues/2024-12-10-jira-upgrade-and-restart/</link><pubDate>Wed, 11 Dec 2024 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-12-10-jira-upgrade-and-restart/</guid><category>2024-12-11T00:15:00-00:00</category><description>&lt;p&gt;The Jira instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 30 minutes beginning at 00:00 (UTC) Tuesday November 11, 2024 so that it can be upgraded and restarted.&lt;/p&gt;</description></item><item><title>[Resolved] Disruption of mirror selections on get.jenkins.io and Update Center</title><link>https://status.jenkins.io/issues/2024-12-05-mirrorbits-gelocation-disruption/</link><pubDate>Thu, 05 Dec 2024 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-12-05-mirrorbits-gelocation-disruption/</guid><category>2024-12-16T07:40:00-00:00</category><description>&lt;p&gt;User reported that mirror selection is acting randomly with message in mirrorbit web UI saying &amp;ldquo;Cannot locate the client IP (ASN0)&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;Requests are still served but it may disrupt download performances.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4441"&gt;https://github.com/jenkins-infra/helpdesk/issues/4441&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on the Update Center with 404-502 errors</title><link>https://status.jenkins.io/issues/2024-11-28-outage-uc/</link><pubDate>Thu, 28 Nov 2024 08:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-28-outage-uc/</guid><category>2024-11-28T10:30:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;Multiple issues opened such as &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4427"&gt;https://github.com/jenkins-infra/helpdesk/issues/4427&lt;/a&gt; or &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4428"&gt;https://github.com/jenkins-infra/helpdesk/issues/4428&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Remediation consisted in cordoning and draining the Kubernetes nodes to bypass the CSI SMB/CIFS errors causing the outage.
Long term fix has been applied the 29 Nov.: see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4402"&gt;https://github.com/jenkins-infra/helpdesk/issues/4402&lt;/a&gt; for details.&lt;/p&gt;
&lt;p&gt;[Initial message]
The update center is having errors 404 and 502, remediation incoming&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://matrix.to/#/!JLUOInpEYmxJIYXlzs:matrix.org/$Uvn4cn3an3RDVQT_trYGbPT3OKdV8yf0NFfjcW_Tejo?via=g4v.dev&amp;amp;via=gitter.im&amp;amp;via=matrix.org"&gt;https://matrix.to/#/!JLUOInpEYmxJIYXlzs:matrix.org/$Uvn4cn3an3RDVQT_trYGbPT3OKdV8yf0NFfjcW_Tejo?via=g4v.dev&amp;amp;via=gitter.im&amp;amp;via=matrix.org&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2024-11-27-ci-maintenance-sec-advisory/</link><pubDate>Wed, 27 Nov 2024 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-27-ci-maintenance-sec-advisory/</guid><category>2024-11-27T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with latest LTS 2.479.2 Core version.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday November 27 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and updated as a result of a security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/KPuGGzCkWX0"&gt;https://groups.google.com/g/jenkinsci-advisories/c/KPuGGzCkWX0&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Datadog plugin upgrade)</title><link>https://status.jenkins.io/issues/2024-11-14-ci-maintenance/</link><pubDate>Thu, 14 Nov 2024 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-14-ci-maintenance/</guid><category>2024-11-14T08:45:00-00:00</category><description>&lt;p&gt;Thursday November 14 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be restarted to upgrade the &lt;code&gt;datadog&lt;/code&gt; plugin as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4377"&gt;https://github.com/jenkins-infra/helpdesk/issues/4377&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If this operation ends up in corrupting the build log like the previous ones, we&amp;rsquo;ll immediately restore the backup and restart the controller.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io (Security Advisory)</title><link>https://status.jenkins.io/issues/2024-11-13-ci-maintenance/</link><pubDate>Wed, 13 Nov 2024 15:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-13-ci-maintenance/</guid><category>2024-11-13T19:15:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday November 13 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and restarted if plugin updates are needed as a result of a plugin security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/UmiH1ZpJez4"&gt;https://groups.google.com/g/jenkinsci-advisories/c/UmiH1ZpJez4&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) upgrade and restart</title><link>https://status.jenkins.io/issues/2024-11-11-jira-upgrade-and-restart/</link><pubDate>Mon, 11 Nov 2024 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-11-jira-upgrade-and-restart/</guid><category>2024-11-11T23:59:00-00:00</category><description>&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 15 minutes beginning at 23:00 (UTC) Monday November 11, 2024 so that it can be upgraded and restarted.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (6)</title><link>https://status.jenkins.io/issues/2024-11-07-uc-24hour-brownout-6/</link><pubDate>Thu, 07 Nov 2024 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-11-07-uc-24hour-brownout-6/</guid><category>2024-11-08T09:00:00-00:00</category><description>&lt;p&gt;Thursday 07 November 2024 at 09:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system for 24 hours.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (5)</title><link>https://status.jenkins.io/issues/2024-10-24-uc-24hour-brownout-5/</link><pubDate>Thu, 24 Oct 2024 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-10-24-uc-24hour-brownout-5/</guid><category>2024-10-25T10:00:00-00:00</category><description>&lt;p&gt;Thursday 24 October 2024 at 10:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system for 24 hours.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [get.jenkins.io] Reset mirrors database</title><link>https://status.jenkins.io/issues/2024-10-16-get-jenkins-io-redis-cleanup/</link><pubDate>Wed, 16 Oct 2024 12:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-10-16-get-jenkins-io-redis-cleanup/</guid><category>2024-10-16T16:20:00-00:00</category><description>&lt;p&gt;Thursday October 30 2024, starting at 12:45 UTC, the Jenkins download website (get.jenkins.io/mirrors.jenkins.io) will be disrupted for a technical operation on its database.&lt;/p&gt;
&lt;p&gt;The goal is to solve the HTTP/404 errors on old files caught in the following issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4330"&gt;https://github.com/jenkins-infra/helpdesk/issues/4330&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The Jenkins Infra team does not expect and outage but slower download as all traffic will be sent to the fallback system until mirrors are added back and fully scanned.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4330"&gt;https://github.com/jenkins-infra/helpdesk/issues/4330&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-10-02-ci.jenkins.io-outage/</link><pubDate>Wed, 02 Oct 2024 11:19:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-10-02-ci.jenkins.io-outage/</guid><category>2024-10-02T13:10:00-00:00</category><description>&lt;p&gt;Jenkins core update is being applied for the &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/dszNG7XKdKU/m/IvT63YLiAgAJ"&gt;Jenkins security advisory&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (4)</title><link>https://status.jenkins.io/issues/2024-09-25-uc-24hour-brownout-4/</link><pubDate>Thu, 26 Sep 2024 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-09-25-uc-24hour-brownout-4/</guid><category>2024-09-27T07:00:00-00:00</category><description>&lt;p&gt;Thursday 26 September 2024 at 07:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system for 24 hours.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (3)</title><link>https://status.jenkins.io/issues/2024-09-10-uc-24hour-brownout-3/</link><pubDate>Wed, 11 Sep 2024 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-09-10-uc-24hour-brownout-3/</guid><category>2024-09-12T14:00:00-00:00</category><description>&lt;p&gt;Wednesday 11 September 2024 from 02:00pm UTC until Thursday 12 September 2024 02:00pm UTC,
the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt; and &lt;a href="https://www.jenkins.io/blog/2024/09/10/update-center-brownouts-3/"&gt;https://www.jenkins.io/blog/2024/09/10/update-center-brownouts-3/&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Azure VMs outage</title><link>https://status.jenkins.io/issues/2024-09-09-azure-vms-outage/</link><pubDate>Mon, 09 Sep 2024 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-09-09-azure-vms-outage/</guid><category>2024-09-13T21:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Azure did fix the problem in two steps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Additional capacity added in US East 2 the 12 September&lt;/li&gt;
&lt;li&gt;Software fix the 13 September&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Update on 2024-09-10]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The problem was gone from 2024-09-09 around 11:00pm UTC but it&amp;rsquo;s back since 2024-09-10 around 02:00pm UTC&lt;/li&gt;
&lt;li&gt;Our Azure Service Health Dashboard mentions 2 mixed incidents, one should be fixed the 12!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[initial message]
Since Monday 9 September 2024 at 03:00pm UTC, we see an increased rate of failure to spin up Azure VM agents on ci.jenkins.io&lt;/p&gt;
&lt;p&gt;Details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4287"&gt;https://github.com/jenkins-infra/helpdesk/issues/4287&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (2)</title><link>https://status.jenkins.io/issues/2024-09-09-uc-1hour-brownout-2/</link><pubDate>Mon, 09 Sep 2024 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-09-09-uc-1hour-brownout-2/</guid><category>2024-09-09T15:05:00-00:00</category><description>&lt;p&gt;Monday 9 September 2024 at 02:00pm UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system during 1 hour.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center Brownout (1)</title><link>https://status.jenkins.io/issues/2024-09-06-uc-1hour-brownout-1/</link><pubDate>Fri, 06 Sep 2024 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-09-06-uc-1hour-brownout-1/</guid><category>2024-09-06T08:00:00-00:00</category><description>&lt;p&gt;Friday 6 September 2024 at 07:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will switch its implementation to a new system during 1 hour.&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.&lt;/p&gt;
&lt;p&gt;⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.&lt;/p&gt;
&lt;p&gt;Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2649"&gt;https://github.com/jenkins-infra/helpdesk/issues/2649&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Azure AKS cluster `publick8s` to 1.29</title><link>https://status.jenkins.io/issues/2024-08-23-maintenance-az-publick8s-1-29/</link><pubDate>Fri, 23 Aug 2024 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-23-maintenance-az-publick8s-1-29/</guid><category>2024-08-23T09:40:00-00:00</category><description>&lt;p&gt;Friday 23 August at 07:30am UTC, the AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded to Kubernetes 1.29.7. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4161"&gt;https://github.com/jenkins-infra/helpdesk/issues/4161&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Azure AKS cluster `privatek8s` to 1.29</title><link>https://status.jenkins.io/issues/2024-08-23-maintenance-az-privatek8s-1-29/</link><pubDate>Fri, 23 Aug 2024 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-23-maintenance-az-privatek8s-1-29/</guid><category>2024-08-23T08:15:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade finished with success.&lt;/p&gt;
&lt;p&gt;[Initial message]
Friday 23 August at 07:30am UTC, the AKS cluster &lt;code&gt;privatek8s&lt;/code&gt; will be upgraded to Kubernetes 1.29.7. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;Expect multiple restarts and downtimes for the infra.ci.jenkins.io and release.ci.jenkins.io controllers along with the rss2twitter, ircbot and github-comment-ops bots.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4161"&gt;https://github.com/jenkins-infra/helpdesk/issues/4161&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] [ci.jenkins.io container agents] AKS Upgrade to Kubernetes 1.29.7</title><link>https://status.jenkins.io/issues/2024-08-22-maintenance-aks-cijioagents1-1-29/</link><pubDate>Thu, 22 Aug 2024 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-22-maintenance-aks-cijioagents1-1-29/</guid><category>2024-08-22T14:40:00-00:00</category><description>&lt;p&gt;Thursday 22 August 2024, at 14:00 UTC, we&amp;rsquo;ll upgrade the AKS cluster hosting ci.jenkins.io&amp;rsquo;s container agents and Artifact Caching proxy to Kubernetes 1.29.7&lt;/p&gt;
&lt;p&gt;All agents using &lt;code&gt;jnlp-linux-*&lt;/code&gt; or &lt;code&gt;jnlp-bom&lt;/code&gt; labels, or pipelines with the &lt;code&gt;buildPlugin()&lt;/code&gt; function with &lt;code&gt;useContainer: true&lt;/code&gt; will be queued until the end of the operation.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4161#issuecomment-2304516597"&gt;https://github.com/jenkins-infra/helpdesk/issues/4161#issuecomment-2304516597&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-08-22-ci-maintenance/</link><pubDate>Thu, 22 Aug 2024 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-22-ci-maintenance/</guid><category>2024-08-22T13:30:00-00:00</category><description>&lt;p&gt;Thursday August 22 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be restarted to upgrade the &lt;code&gt;datadog&lt;/code&gt; plugin as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4236"&gt;https://github.com/jenkins-infra/helpdesk/issues/4236&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If this operation ends up in corrupting the build log like the previous ones, we&amp;rsquo;ll immediately restore the backup and restart the controller.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-08-07-ci-maintenance/</link><pubDate>Wed, 07 Aug 2024 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-07-ci-maintenance/</guid><category>2024-08-07T11:37:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins and Core.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday August 07 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and restarted if plugin updates are needed as a result of a plugin security advisory.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/NkXElf7MmcI"&gt;https://groups.google.com/g/jenkinsci-advisories/c/NkXElf7MmcI&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] ldap.jio and repo.azure.jio workloads migration to arm64 (publick8s cluster)</title><link>https://status.jenkins.io/issues/2024-07-05-maintenance-az-publick8s-arm64/</link><pubDate>Fri, 05 Jul 2024 14:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-05-maintenance-az-publick8s-arm64/</guid><category>2024-07-05T15:30:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re doing a workload migration to &lt;code&gt;arm64&lt;/code&gt; on the publick8s AKS cluster starting at 14:30 UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io (ACP)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3837#issuecomment-2210532769"&gt;https://github.com/jenkins-infra/helpdesk/issues/3837#issuecomment-2210532769&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update azure clusters publick8s Kubernetes version to 1.28</title><link>https://status.jenkins.io/issues/2024-07-03-maintenance-az-publick8s-1-28/</link><pubDate>Thu, 04 Jul 2024 06:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-03-maintenance-az-publick8s-1-28/</guid><category>2024-07-04T7:15:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 7:15am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746"&gt;https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.27 to 1.28 tomorrow, 4th of July 2024, starting at 6:30 UTC (8h30 paris time, 12h00 IST).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Jenkins Core Release 2.465 failed</title><link>https://status.jenkins.io/issues/2024-07-02-weekly-core-release-2.465-failed/</link><pubDate>Tue, 02 Jul 2024 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-02-weekly-core-release-2.465-failed/</guid><category>2024-07-02T20:00:00-00:00</category><description>&lt;p&gt;[Final]
GH releases published for the Docker Image: &lt;a href="https://github.com/jenkinsci/docker/releases/tag/2.466"&gt;https://github.com/jenkinsci/docker/releases/tag/2.466&lt;/a&gt; (and &lt;a href="https://github.com/jenkinsci/docker/releases/tag/2.465"&gt;https://github.com/jenkinsci/docker/releases/tag/2.465&lt;/a&gt; marked as burnt)&lt;/p&gt;
&lt;p&gt;[Update]
The issue seems to be related to a Maven plugin version bump. The release 2.465 is considered burnt and we are starting 2.466 release as a replacement.&lt;/p&gt;
&lt;p&gt;[Initial message]
The Jenkins Core weekly release 2.465 failed. We are investigating.&lt;/p&gt;</description></item><item><title>[Resolved] Plugins Health Score not computed</title><link>https://status.jenkins.io/issues/2024-07-02-publicheathscore-outage/</link><pubDate>Tue, 02 Jul 2024 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-02-publicheathscore-outage/</guid><category>2024-10-11T11:00:00-00:00</category><description>&lt;p&gt;[Initial message]
The Plugin Health scores are not computed since some times. We are investigating the issue.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4152"&gt;https://github.com/jenkins-infra/helpdesk/issues/4152&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on weekly.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-07-01-weeklyci-maintenance/</link><pubDate>Mon, 01 Jul 2024 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-01-weeklyci-maintenance/</guid><category>2024-07-01T12:45:00-00:00</category><description>&lt;p&gt;[Final message]
Migration done successfully&lt;/p&gt;
&lt;p&gt;[Initial message]
The &lt;code&gt;weekly.ci.jenkins.io&lt;/code&gt; controller will be down for a data volume operation starting at 12:30pm.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4044"&gt;https://github.com/jenkins-infra/helpdesk/issues/4044&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] High rate of HTTP/502 errors on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-07-01-ci-incident/</link><pubDate>Mon, 01 Jul 2024 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-01-ci-incident/</guid><category>2024-07-01T09:30:00-00:00</category><description>&lt;p&gt;[Final message]
The issue has been resolved after a few restarts (and fixes of course!)&lt;/p&gt;
&lt;p&gt;[Initial message]
We are investigating a high rate of HTTP/502 errors on ci.jenkins.io. We&amp;rsquo;ll keep you posted.&lt;/p&gt;
&lt;p&gt;Expect multiple restarts and outage.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4158"&gt;https://github.com/jenkins-infra/helpdesk/issues/4158&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update azure clusters privatek8s Kubernetes version to 1.28</title><link>https://status.jenkins.io/issues/2024-06-27-maintenance-az-privatek8s-1-28/</link><pubDate>Thu, 27 Jun 2024 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-06-27-maintenance-az-privatek8s-1-28/</guid><category>2024-06-27T08:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade finished with success.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re doing an privatek8s AZ cluster upgrade from 1.27 to 1.28 today 27th of June 2024, starting at 07:00 UTC
worst case scenario 20mn downtime&lt;/p&gt;</description></item><item><title>[Resolved] issues.jenkins.io (Jira) upgrade</title><link>https://status.jenkins.io/issues/2024-06-26-jira-upgrade/</link><pubDate>Wed, 26 Jun 2024 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-06-26-jira-upgrade/</guid><category>2024-06-26T23:45:00-00:00</category><description>&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;The Jira issue tracker at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 45 minutes beginning at 23:00 (UTC) Wednesday June 26, 2024.
The Jira issue tracker will be upgraded to a newer release.&lt;/p&gt;
&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;Upgrade was successful.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-06-26-ci-maintenance/</link><pubDate>Wed, 26 Jun 2024 11:30:11 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-06-26-ci-maintenance/</guid><category>2024-06-26T16:35:11-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins.&lt;/p&gt;
&lt;p&gt;[Update]
The update is taking longer than planned, expect a restart around 16h30 UTC.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday June 26 2024, the &lt;code&gt;ci.jenkins.io&lt;/code&gt; controller will be put offline and restarted if plugin updates are needed as a result of the plugin security advisory.&lt;/p&gt;
&lt;p&gt;The restart may happen between 11:30am UTC and 15:30 UTC.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/MokuNdWXGfg"&gt;https://groups.google.com/g/jenkinsci-advisories/c/MokuNdWXGfg&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io operation on container agents (Kubernetes 1.28)</title><link>https://status.jenkins.io/issues/2024-06-25-maintenance-aks-k8s-cijioa-1-28/</link><pubDate>Tue, 25 Jun 2024 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-06-25-maintenance-aks-k8s-cijioa-1-28/</guid><category>2024-06-25T08:45:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade finished.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re (infra team) doing an AKS clusters upgrade from 1.27 to 1.28 the Tuesday 25th of June 2024, starting at 08:00 UTC (10h paris time).
It will impact the ci.jenkins.io container agents (both &lt;code&gt;jnlp-linux-*&lt;/code&gt; and &lt;code&gt;jnlp-bom&lt;/code&gt; templates) but the VM agents will still be available.&lt;/p&gt;</description></item><item><title>[Resolved] Repository Permission Updater on trusted.jenkins.io</title><link>https://status.jenkins.io/issues/2024-06-05-rpu-trusted/</link><pubDate>Tue, 04 Jun 2024 20:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-06-05-rpu-trusted/</guid><category>2024-05-06T17:35:00-00:00</category><description>&lt;p&gt;As per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4122"&gt;https://github.com/jenkins-infra/helpdesk/issues/4122&lt;/a&gt;, trusted.jenkins.io&amp;rsquo;s RPU builds are stuck since an update, the token to publish plugins are not delivered.&lt;/p&gt;</description></item><item><title>[Resolved] Downgrading `datadog` plugin on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-05-06-ci.jenkins.io-datadog-plugin/</link><pubDate>Mon, 06 May 2024 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-05-06-ci.jenkins.io-datadog-plugin/</guid><category>2024-05-06T12:05:00-00:00</category><description>&lt;p&gt;As per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4080#issuecomment-2095831304"&gt;https://github.com/jenkins-infra/helpdesk/issues/4080#issuecomment-2095831304&lt;/a&gt;, ci.jenkins.io will be down for an operation trying to fix the corrupted builds.&lt;/p&gt;
&lt;p&gt;A first tentative will be done to downgrade the &lt;code&gt;datadog&lt;/code&gt; plugin, if it fails then the plugin will be removed.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-05-02-ci.jenkins.io-outage/</link><pubDate>Thu, 02 May 2024 10:53:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-05-02-ci.jenkins.io-outage/</guid><category>2024-05-02T12:58:00-00:00</category><description>&lt;p&gt;Plugin updates are being applied for the Jenkins security advisory.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-04-23-ci-maintenance/</link><pubDate>Tue, 23 Apr 2024 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-04-23-ci-maintenance/</guid><category>2024-04-23T16:20:00-00:00</category><description>&lt;p&gt;The ci.jenkins.io controller will have builds waiting in the queue during a maintenance for configuration upgrade.
Until the Azure credentials are fully rotated, no VM agent will be spawned.
Container agents will continue to work as expected.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4052"&gt;https://github.com/jenkins-infra/helpdesk/issues/4052&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on infra.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-04-11-infraci-maintenance/</link><pubDate>Thu, 11 Apr 2024 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-04-11-infraci-maintenance/</guid><category>2024-04-11T10:00:00-00:00</category><description>&lt;p&gt;[Final message]
Migration face multiple issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;needed PV/PVC creation on the disk from snapshot before cloning by the jenkins helmchart&lt;/li&gt;
&lt;li&gt;needed some optimization to deal with timout on volume mount &lt;a href="https://github.com/jenkinsci/helm-charts/tree/a052ad9f6fc0f95e67802edc7cef9ab9c3572bee/charts/jenkins#long-volume-attachmount-times"&gt;https://github.com/jenkinsci/helm-charts/tree/a052ad9f6fc0f95e67802edc7cef9ab9c3572bee/charts/jenkins#long-volume-attachmount-times&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;The infra.ci.jenkins.io controller will be down to migrate the volume used to ZRS as per&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3823#issuecomment-2036372624"&gt;https://github.com/jenkins-infra/helpdesk/issues/3823#issuecomment-2036372624&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Artifact Caching Proxy deployment of 1.0.0</title><link>https://status.jenkins.io/issues/2024-03-28-acp-1.0.0/</link><pubDate>Thu, 28 Mar 2024 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-28-acp-1.0.0/</guid><category>2024-03-28T07:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade successfull&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3969#issuecomment-2024586947"&gt;https://github.com/jenkins-infra/helpdesk/issues/3969#issuecomment-2024586947&lt;/a&gt; for details.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;The Artifact Caching Proxy system used by ci.jenkins.io and infra.ci.jenkins.io agents to cache Maven artifacts will upgraded to version 1.0.0 the 28 March 2024 at 07:30am UTC.&lt;/p&gt;
&lt;p&gt;Expect eventual slowness or failures in Maven dependency resolutions in the next hour on ci.jenkins.io and infra.ci.jenkins.io.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3969#issuecomment-2024586947"&gt;https://github.com/jenkins-infra/helpdesk/issues/3969#issuecomment-2024586947&lt;/a&gt; for details.&lt;/p&gt;</description></item><item><title>[Resolved] update center maintenance</title><link>https://status.jenkins.io/issues/2024-03-25-update-center-maintenance/</link><pubDate>Mon, 25 Mar 2024 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-25-update-center-maintenance/</guid><category>2024-03-25T14:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Migration finished.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3414"&gt;https://github.com/jenkins-infra/helpdesk/issues/3414&lt;/a&gt; for more details.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll migrate scripts used by the update center from blobxfer to azcopy today at 13h30 UTC, which might result in a latency of plugins new releases availability.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3414"&gt;https://github.com/jenkins-infra/helpdesk/issues/3414&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Update azure clusters publick8s Kubernetes version to 1.27</title><link>https://status.jenkins.io/issues/2024-03-19-maintenance-az-publick8s-1-27/</link><pubDate>Tue, 19 Mar 2024 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-19-maintenance-az-publick8s-1-27/</guid><category>2024-03-19T9:35:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 9:35am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964"&gt;https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.26 to 1.27 today 19th of Mars 2024, starting at 8:30 UTC (9h30 paris time).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Update azure clusters privatek8s Kubernetes version to 1.27</title><link>https://status.jenkins.io/issues/2024-03-18-maintenance-az-privatek8s-1-27/</link><pubDate>Mon, 18 Mar 2024 15:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-18-maintenance-az-privatek8s-1-27/</guid><category>2024-03-18T16:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade finished.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an privatek8s AZ cluster upgrade from 1.26 to 1.27 today 18th of Mars 2024, starting at 15:30 UTC (16h30 paris time).
worst case scenario 20mn downtime&lt;/p&gt;</description></item><item><title>[Resolved] issues.jenkins.io (Jira) upgrade</title><link>https://status.jenkins.io/issues/2024-03-12-jira-upgrade/</link><pubDate>Tue, 12 Mar 2024 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-12-jira-upgrade/</guid><category>2024-03-12T23:28:00-00:00</category><description>&lt;p&gt;The Jira instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 3 hours beginning at 23:00 (UTC) Tuesday March 12, 2024.
The Jira instance will be upgraded to a newer release.
Track the upgrade on the &lt;a href="https://status.linuxfoundation.org/incidents/d6c890x0lrlp"&gt;Linux Foundation status page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update AKS clusters Kubernetes version to 1.27</title><link>https://status.jenkins.io/issues/2024-03-07-maintenance-aks-k8s-1-27/</link><pubDate>Thu, 07 Mar 2024 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-07-maintenance-aks-k8s-1-27/</guid><category>2024-03-07T10:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Upgrade finished.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an AKS clusters upgrade from 1.26 to 1.27 the Thursday 07th of Mars 2024, starting at 08:00 UTC (9h paris time).&lt;/p&gt;</description></item><item><title>[Resolved] plugins.jenkins.io storage migration</title><link>https://status.jenkins.io/issues/2024-02-28-plugins.jenkins.io-storage-account-migration/</link><pubDate>Wed, 28 Feb 2024 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-02-28-plugins.jenkins.io-storage-account-migration/</guid><category>2024-02-28T11:10:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Migration finished, no service disruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;ll migrate the storage of plugins.jenkins.io today at 11h00 UTC, which might result in a brief service disruption.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3414"&gt;https://github.com/jenkins-infra/helpdesk/issues/3414&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] jenkins.io storage migration</title><link>https://status.jenkins.io/issues/2024-02-26-jenkins.io-storage-account-migration/</link><pubDate>Mon, 26 Feb 2024 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-02-26-jenkins.io-storage-account-migration/</guid><category>2024-02-26T13:45:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Migration finished, no service disruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;ll migrate the storage of jenkins.io today at 13h30 UTC, which might result in a brief service disruption.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3414"&gt;https://github.com/jenkins-infra/helpdesk/issues/3414&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io is down</title><link>https://status.jenkins.io/issues/2024-02-07-ci-down/</link><pubDate>Wed, 07 Feb 2024 14:40:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-02-07-ci-down/</guid><category>2024-02-07T15:20:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;The ci.jenkins.io controller is up again.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;The ci.jenkins.io controller is down, we&amp;rsquo;re working on it.&lt;/p&gt;</description></item><item><title>[Resolved] get.jenkins.io latest 2.443 issue</title><link>https://status.jenkins.io/issues/2024-01-30-get-jenkins-io-latest-issue/</link><pubDate>Tue, 30 Jan 2024 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-30-get-jenkins-io-latest-issue/</guid><category>2024-01-30T21:50:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;Release Core packaging process finished with success, both services are back to normal.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;Tuesday January 30 2024, starting at 15:05 UTC, get.jenkins.io and updates.jenkins.io return an error when trying to download the latest Jenkins Weekly release 2.443, due to an issue in the release process.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3927"&gt;https://github.com/jenkins-infra/helpdesk/issues/3927&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] get(mirrors).jenkins.io storage migration</title><link>https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/</link><pubDate>Fri, 26 Jan 2024 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/</guid><category>2024-01-26T12:15:00-00:00</category><description>&lt;p&gt;A maintenance on get.jenkins.io (mirrors.jenkins*) will be performed with a &lt;strong&gt;partial service disruption&lt;/strong&gt; the Friday 26 January 2024 starting at 12:00pm (noon time) UTC.&lt;/p&gt;
&lt;p&gt;The goal of this maintenance is to migrate the underlying storage to a new system in Azure.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3917"&gt;https://github.com/jenkins-infra/helpdesk/issues/3917&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of ci.jenkins.io VM to another location</title><link>https://status.jenkins.io/issues/2024-01-25-ci.jenkins.io-migration/</link><pubDate>Thu, 25 Jan 2024 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-25-ci.jenkins.io-migration/</guid><category>2024-01-25T14:30:00-00:00</category><description>&lt;p&gt;A maintenance on ci.jenkins.io will be performed with a &lt;strong&gt;full service disruption&lt;/strong&gt; the Thursday 25 January 2024 starting at 12:30pm (noon time) UTC.&lt;/p&gt;
&lt;p&gt;The goal of this maintenance is to migrate ci.jenkins.io VM to a new location in Azure.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3913"&gt;https://github.com/jenkins-infra/helpdesk/issues/3913&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2024-01-24-ci-maintenance/</link><pubDate>Wed, 24 Jan 2024 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-24-ci-maintenance/</guid><category>2024-01-24T11:50:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;The ci.jenkins.io controller has been updated and is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;The ci.jenkins.io controller is down for maintenance as part of a security upgrade announced in&lt;/p&gt;
&lt;p&gt;&lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/QZiecB2ArMs/m/sDvJWIdHBQAJ"&gt;https://groups.google.com/g/jenkinsci-advisories/c/QZiecB2ArMs/m/sDvJWIdHBQAJ&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] LDAP (ldap.jenkins.io) maintenance</title><link>https://status.jenkins.io/issues/2024-01-19-ldap-maintenance/</link><pubDate>Fri, 19 Jan 2024 08:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-19-ldap-maintenance/</guid><category>2024-01-19T10:15:00-00:00</category><description>&lt;p&gt;Friday January 19 2024, starting at 08:45am UTC, we&amp;rsquo;ll proceed to a maintenance on the LDAP service (&lt;code&gt;ldap.jenkins.io&lt;/code&gt;) hosted in the &lt;code&gt;publick8s&lt;/code&gt; Azure Kubernetes cluster.&lt;/p&gt;
&lt;p&gt;Authentication on all of the &lt;code&gt;*.jenkins.io&lt;/code&gt; and &lt;code&gt;*.jenkins-ci.orf&lt;/code&gt; services will be unavailable during the operation.
We expect a disruption between 5 and 30 min.&lt;/p&gt;
&lt;p&gt;The goal is to update the LDAP image to a new version to use a new deployment system.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3837#issuecomment-1898378430"&gt;https://github.com/jenkins-infra/helpdesk/issues/3837#issuecomment-1898378430&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] get.jenkins.io maintenance</title><link>https://status.jenkins.io/issues/2024-01-08-get-jenkins-io-maintenance/</link><pubDate>Mon, 08 Jan 2024 15:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-08-get-jenkins-io-maintenance/</guid><category>2024-01-09T12:00:00-00:00</category><description>&lt;p&gt;[Final Message]
THe migration is finally finished at noon UTC the 09th.
There were 2 downtimes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;2 min the 8th around 17:30 UTC (TLS errors) due to a missing ingress configuration&lt;/li&gt;
&lt;li&gt;5 min the 9th around 11:50 UTC (HTTP/500 errors) due to a race condition in helm chart deployments&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
Monday January 8 2024, starting at 15:15 UTC, we&amp;rsquo;ll proceed to a maintenance on the service &lt;code&gt;get.jenkins.io&lt;/code&gt; hosted in the &lt;code&gt;publick8s&lt;/code&gt; Azure Kubernetes cluster.&lt;/p&gt;
&lt;p&gt;The following services will be slower to respond or even might be disrupted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;mirrors.jenkins-ci.org (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;mirrors.jenkins.io (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;fallback.get.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The goal is to change the helm chart use to deploy the service from the legacy &lt;code&gt;mirrorbits&lt;/code&gt; to the new &lt;code&gt;mirrorbits-parent&lt;/code&gt; to benefit from:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Apache running in &lt;code&gt;arm64&lt;/code&gt; Linux systems (cheaper)&lt;/li&gt;
&lt;li&gt;Readonly filesystem for shared data (safety)&lt;/li&gt;
&lt;li&gt;Same features as the current updates-jenkins-io service (maintenance and sustainability)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3828"&gt;https://github.com/jenkins-infra/helpdesk/issues/3828&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] issues.jenkins.io (Jira) upgrade</title><link>https://status.jenkins.io/issues/2023-12-29-jira-upgrade/</link><pubDate>Fri, 29 Dec 2023 18:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-29-jira-upgrade/</guid><category>2023-12-29T18:30:00-00:00</category><description>&lt;p&gt;The Jira instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 30 minutes beginning at 18:00 (UTC) Friday December 29, 2023.
The Jira instance will be upgraded to a newer release.&lt;/p&gt;</description></item><item><title>[Resolved] issues.jenkins.io (Jira) upgrade</title><link>https://status.jenkins.io/issues/2023-12-27-jira-upgrade/</link><pubDate>Wed, 27 Dec 2023 18:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-27-jira-upgrade/</guid><category>2023-12-27T20:00:00-00:00</category><description>&lt;p&gt;The Jira instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to two hours beginning at 18:00 (UTC) Wednesday December 27, 2023 so that it can be upgraded.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2023-12-18-jira-outage/</link><pubDate>Mon, 18 Dec 2023 17:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-18-jira-outage/</guid><category>2023-12-18T19:00:00-00:00</category><description>&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to two hours beginning at 17:00 (UTC) Monday December 18, 2023 so that it can be restored from backup.
A spammer damaged over 1000 Jenkins issue reports on Dec 6, 2023.
A database backup will be restored that precedes the damage.&lt;/p&gt;</description></item><item><title>[Resolved] Removal of the Maven Central mirrored repositories from JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2023-12-15-artifactory-changes/</link><pubDate>Fri, 15 Dec 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-15-artifactory-changes/</guid><category>2023-12-15T15:00:00-00:00</category><description>&lt;p&gt;Friday December 15, 2023 at 13:00 UTC, we&amp;rsquo;ll change the configuration of the Jenkins Artifactory service at repo.jenkins-ci.org.&lt;/p&gt;
&lt;p&gt;We will remove all mirrors of the &lt;a href="https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/"&gt;jcenter artifact repository&lt;/a&gt; and the oss.sonatype.org-releases repository from repo.jenkins-ci.org to force Maven builds to download artifacts that are provided by Maven Central from the Maven central repository instead of our Artifactory instance.&lt;/p&gt;
&lt;p&gt;This is part of the effort to decrease outbound bandwidth used by the Jenkins Artifactory service.
Refer to the &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3842"&gt;removal plan&lt;/a&gt; for more details and to the &lt;a href="https://groups.google.com/g/jenkinsci-dev/c/Jn_4U-KQUqg/m/N5i6VH7_AAAJ"&gt;announcement in the developer mailing list&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-12-13-ci.jenkins.io-outage/</link><pubDate>Wed, 13 Dec 2023 12:54:47 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-13-ci.jenkins.io-outage/</guid><category>2023-12-13T13:27:00-00:00</category><description>&lt;p&gt;Outage is being investigated.
High CPU load was detected.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2023-12-07-jira-outage/</link><pubDate>Thu, 07 Dec 2023 22:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-07-jira-outage/</guid><category>2023-12-07T22:30:00-00:00</category><description>&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 30 minutes beginning at 10:00 PM (UTC) Thursday December 7, 2023 so that it can be upgraded.&lt;/p&gt;</description></item><item><title>[Resolved] AKS (`publick8s`) operation on the x86 nodes</title><link>https://status.jenkins.io/issues/2023-12-07-x86medium-migration/</link><pubDate>Thu, 07 Dec 2023 10:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-07-x86medium-migration/</guid><category>2023-12-07T11:15:00-00:00</category><description>&lt;p&gt;[FINAL]
Operation finished with success&lt;/p&gt;
&lt;p&gt;[INITIAL]
Thursday December 7 2023, starting at 10:30am UTC, we&amp;rsquo;ll proceed to the amd/intel migration from x86medium nodepool to x86small nodepool&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3827"&gt;https://github.com/jenkins-infra/helpdesk/issues/3827&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Brownout of the Maven Central mirrored repositories in JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2023-12-06-artifactory-central-brownount/</link><pubDate>Wed, 06 Dec 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-06-artifactory-central-brownount/</guid><category>2023-12-06T15:00:00-00:00</category><description>&lt;p&gt;Wednesday December 6, 2023, we&amp;rsquo;ll perform a &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;brownout&lt;/a&gt; operation of 2 hours on the Jenkins Artifactory service at repo.jenkins-ci.org at 13:00 UTC.&lt;/p&gt;
&lt;p&gt;The brownout will remove all mirrors of the &lt;a href="https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/"&gt;jcenter artifact repository&lt;/a&gt; from repo.jenkins-ci.org to force Maven builds to download artifacts that are provided by Maven Central from the Maven central repository instead of our Artifactory instance.&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;planned brownout&lt;/a&gt; is part of the effort to decrease outbound bandwidth used by the Jenkins Artifactory service.
Refer to the &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3842"&gt;removal plan&lt;/a&gt; for more details and to the &lt;a href="https://groups.google.com/g/jenkinsci-dev/c/Jn_4U-KQUqg/m/N5i6VH7_AAAJ"&gt;announcement in the developer mailing list&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] operation on systempool publick8s</title><link>https://status.jenkins.io/issues/2023-12-06-systempool-tainted/</link><pubDate>Wed, 06 Dec 2023 09:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-06-systempool-tainted/</guid><category>2023-12-05T11:15:00-00:00</category><description>&lt;p&gt;Wednesday December 6 2023, starting at 9:15 UTC (10:15 Paris), we&amp;rsquo;ll proceed to the update of terraform with the new systempool with taint.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3827"&gt;https://github.com/jenkins-infra/helpdesk/issues/3827&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] migration from nodepool x86medium to x86small</title><link>https://status.jenkins.io/issues/2023-12-05-x86medium-migration/</link><pubDate>Tue, 05 Dec 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-05-x86medium-migration/</guid><category>2023-12-05T13:20:00-00:00</category><description>&lt;p&gt;[FINAL]
Aborted as not enough team members available to secure the operation&lt;/p&gt;
&lt;p&gt;[INITIAL]
Tuesday December 5 2023, starting at 13:00 UTC (14:00 Paris), we&amp;rsquo;ll proceed to the amd/intel migration from x86medium nodepool to x86small nodepool with a migration of the old systempool to the new one with taint.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3827"&gt;https://github.com/jenkins-infra/helpdesk/issues/3827&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] migration from nodepool x86medium to x86small</title><link>https://status.jenkins.io/issues/2023-12-04-x86medium-migration/</link><pubDate>Mon, 04 Dec 2023 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-12-04-x86medium-migration/</guid><category>2023-12-04T10:00:00-00:00</category><description>&lt;p&gt;[CLOSING]
operation postpone, new systempool have been create, migration will occur later.&lt;/p&gt;
&lt;p&gt;[INITIAL]
Tuesday December 5 2023, starting at 8:00 UTC (09:00 Paris), we&amp;rsquo;ll proceed to the amd/intel migration from x86medium nodepool to x86small nodepool&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3827"&gt;https://github.com/jenkins-infra/helpdesk/issues/3827&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of weekly.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-11-27-weekly-ci-arm64-migration/</link><pubDate>Mon, 27 Nov 2023 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-27-weekly-ci-arm64-migration/</guid><category>2023-11-27T16:00:00-00:00</category><description>&lt;p&gt;[FINAL message]
Operation successfull&lt;/p&gt;
&lt;p&gt;[INITIAL message]
Monday November 27 2023, starting at 15:00 UTC (16:00 Paris), we&amp;rsquo;ll proceed to the arm64 migration of the weekly.ci.jenkins.io service with volume migration&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Operation on Jenkins Azure VM Controllers</title><link>https://status.jenkins.io/issues/2023-11-22-azure-jenkins-controllers-ops/</link><pubDate>Wed, 22 Nov 2023 14:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-22-azure-jenkins-controllers-ops/</guid><category>2023-11-22T16:30:00-00:00</category><description>&lt;p&gt;Wednesday November 22 2023, starting at 14:30 UTC, an operation on the Jenkins Azure VM controllers will happen.&lt;/p&gt;
&lt;p&gt;No expected impact except delays in the Azure VM and ACI container agent allocation.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3818#issuecomment-1814901484"&gt;https://github.com/jenkins-infra/helpdesk/issues/3818#issuecomment-1814901484&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of weekly.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-11-20-weekly-ci-arm64-migration-v2/</link><pubDate>Tue, 21 Nov 2023 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-20-weekly-ci-arm64-migration-v2/</guid><category>2023-11-21T18:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Operation aborted, we&amp;rsquo;ve identified the issue but it needs more work.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Tuesday November 21 2023, starting at 16:00 UTC (17h00 Paris Time), we&amp;rsquo;ll proceed to the second attempt of arm64 migration of the weekly.ci.jenkins.io service.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of weekly.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-11-20-weekly-ci-arm64-migration/</link><pubDate>Tue, 21 Nov 2023 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-20-weekly-ci-arm64-migration/</guid><category>2023-11-21T09:15:00-00:00</category><description>&lt;p&gt;[Final Message]
Operation aborted due to a &amp;lsquo;volume node affinity&amp;rsquo; problem, need to find out the problem before next try&lt;/p&gt;
&lt;p&gt;[Initial Message]
Tuesday November 21 2023, starting at 8:30 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the weekly.ci.jenkins.io service.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of mirrorbits</title><link>https://status.jenkins.io/issues/2023-11-20-mirrorbits-httpd-rsyncd-arm64-migration/</link><pubDate>Mon, 20 Nov 2023 16:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-20-mirrorbits-httpd-rsyncd-arm64-migration/</guid><category>2023-11-20T16:35:00-00:00</category><description>&lt;p&gt;done without interruption&lt;/p&gt;
&lt;p&gt;Monday November 20 2023, starting at 16:30 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the mirrorbits service not yet in used in production, this should be seemless.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1816831551&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of plugin-site and plugin-site-issues</title><link>https://status.jenkins.io/issues/2023-11-17-pluginsite-arm64-migration/</link><pubDate>Fri, 17 Nov 2023 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-17-pluginsite-arm64-migration/</guid><category>2023-11-17T15:30:00-00:00</category><description>&lt;p&gt;[FINAL message]
all the pods for plugin-site and plugin-site-issues are now on an arm64 nodepool&lt;/p&gt;
&lt;p&gt;[INITIAL message]
Friday November 17 2023, starting at 14:15 UTC, we&amp;rsquo;ll proceed to &lt;a href="https://plugin-site-issues.jenkins.io"&gt;https://plugin-site-issues.jenkins.io&lt;/a&gt; plugins.origin.jenkins.io and migration to arm64.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of the services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1810363708"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619#issuecomment-1810363708&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Update publick8s AKS cluster to Kubernetes 1.26</title><link>https://status.jenkins.io/issues/2023-11-09-maintenance-aks-1.26-publick8s/</link><pubDate>Thu, 09 Nov 2023 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-09-maintenance-aks-1.26-publick8s/</guid><category>2023-11-09T11:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 11:00am UTC.
The monitoring showed an outage of 6 minutes on the LDAP and 2 minutes on the incremental publisher.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680"&gt;https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded from Kubernetes 1.25 to 1.26 the Thursday 09th of November 2023, starting at 08:30am UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Update privatek8s AKS cluster to Kubernetes 1.26</title><link>https://status.jenkins.io/issues/2023-11-07-maintenance-aks-1.26-privatek8s/</link><pubDate>Tue, 07 Nov 2023 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-07-maintenance-aks-1.26-privatek8s/</guid><category>2023-11-07T09:15:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished with success at 09:15am UTC&lt;/p&gt;
&lt;p&gt;[Initial Message]
We&amp;rsquo;re doing an AKS cluster upgrade from 1.25 to 1.26 the Tuesday 07th of November 2023, starting at 08:00am UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;infra.ci.jenkins.io will be down during 20 to 30 min (time for the upgrade to be performed and persistent volumes to be migrated)&lt;/li&gt;
&lt;li&gt;No website preview of &lt;code&gt;*.jenkins.io&lt;/code&gt; on pull requests&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io will be down during 20 to 30 min (time for the upgrade to be performed and persistent volumes to be migrated)&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] arm64 migration of datadog-cluster-agent</title><link>https://status.jenkins.io/issues/2023-11-06-datadog-cluster-agent-arm64-migration/</link><pubDate>Mon, 06 Nov 2023 15:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-06-datadog-cluster-agent-arm64-migration/</guid><category>2023-11-06T15:40:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation finished with success, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Monday November 6 2023, starting at 15:30 UTC, we&amp;rsquo;ll proceed to the datadog cluster agent migration to arm64. (Hosted on publick8s cluster)&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of the services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Update of the AWS EKS Kubernetes clusters to 1.26</title><link>https://status.jenkins.io/issues/2023-11-06-maintenance-eks-k8s-1-26/</link><pubDate>Mon, 06 Nov 2023 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-06-maintenance-eks-k8s-1-26/</guid><category>2023-11-06T16:45:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 16:45 UTC.&lt;/p&gt;
&lt;p&gt;[Initial Message]
An upgrade of the AWS EKS Kubernetes clusters from 1.25 to 1.26 is scheduled the Monday 06 November 2023 at 15:00 UTC.&lt;/p&gt;
&lt;p&gt;Expected impact on ci.jenkins.io:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Usual plugin build workloads using Linux containers will be run in DigitalOcean clusters&lt;/li&gt;
&lt;li&gt;No BOM builds can be run until the operation is finished&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1794913444"&gt;https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1794913444&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Ensure old cached jenkins.io pages are removed</title><link>https://status.jenkins.io/issues/2023-11-02-activate-delete-option-on-jenkins-io-build/</link><pubDate>Fri, 03 Nov 2023 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-02-activate-delete-option-on-jenkins-io-build/</guid><category>2023-11-03T17:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation finished with success, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Update]&lt;/p&gt;
&lt;p&gt;Friday November 3d 2023, starting at 13:30 UTC, we&amp;rsquo;ll activate again an option of jenkins.io build process to ensure old cached jenkins.io pages are removed and not indexed anymore.&lt;/p&gt;
&lt;p&gt;There should not be any interruption of service.&lt;/p&gt;
&lt;p&gt;[Update]&lt;/p&gt;
&lt;p&gt;As removing the outdated content resulted in many old links returning 403 errors, the change has been reverted and the previous state restored.&lt;/p&gt;
&lt;p&gt;Postponing the outdated content deletion while we&amp;rsquo;re working on the next steps described in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3360#issuecomment-1790899357"&gt;https://github.com/jenkins-infra/helpdesk/issues/3360#issuecomment-1790899357&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Thursday November 2d 2023, starting at 13:00 UTC, we&amp;rsquo;ll activate an option of jenkins.io build process to ensure old cached jenkins.io pages are removed and not indexed anymore.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of service.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3360"&gt;https://github.com/jenkins-infra/helpdesk/issues/3360&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of cert-manager</title><link>https://status.jenkins.io/issues/2023-11-06-cert-manager-arm64-migration/</link><pubDate>Tue, 31 Oct 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-06-cert-manager-arm64-migration/</guid><category>2023-11-06T16:45:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation finished with success, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Monday November 6 2023, starting at 15:30 UTC, we&amp;rsquo;ll proceed to the cert manager migration to arm64. (Hosted on publick8s cluster)&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of the services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of uplink</title><link>https://status.jenkins.io/issues/2023-10-31-uplink-arm64-migration/</link><pubDate>Tue, 31 Oct 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-31-uplink-arm64-migration/</guid><category>2023-10-31T14:35:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation finished with success, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Tuesday October 31 2023, starting at 13:00 UTC, we&amp;rsquo;ll proceed to &lt;a href="https://uplink.jenkins.io"&gt;https://uplink.jenkins.io&lt;/a&gt; migration to arm64.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of the services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Preparation of uplink arm64 migration</title><link>https://status.jenkins.io/issues/2023-10-31-uplink-arm64-migration-preparation/</link><pubDate>Tue, 31 Oct 2023 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-31-uplink-arm64-migration-preparation/</guid><category>2023-10-31T10:10:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is finished, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Tuesday October 31 2023, starting at 10:00 UTC, we&amp;rsquo;ll proceed to the deployment of a new uplink image in order to prepare arm64 migration of &lt;a href="https://uplink.jenkins.io"&gt;https://uplink.jenkins.io&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of the services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Update of the Digital Ocean Kubernetes clusters to 1.26</title><link>https://status.jenkins.io/issues/2023-10-26-maintenance-doks-k8s-1-26/</link><pubDate>Thu, 26 Oct 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-26-maintenance-doks-k8s-1-26/</guid><category>2023-10-26T12:45:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 12:45 UTC.&lt;/p&gt;
&lt;p&gt;[Initial Message]
An upgrade of the DigitalOcean Kubernetes clusters from 1.25 to 1.26 is scheduled the Thursday 26 October 2023 at 12:00 (noon) UTC.&lt;/p&gt;
&lt;p&gt;No visible impact is expected on ci.jenkins.io as the container agent workloads will be taken over by the AWS EKS cluster instead of Digital Ocean starting at 11:00 UTC.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1780857936"&gt;https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1780857936&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of mirrorbits</title><link>https://status.jenkins.io/issues/2023-10-25-mirrorbits-arm64-migration/</link><pubDate>Wed, 25 Oct 2023 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-25-mirrorbits-arm64-migration/</guid><category>2023-10-25T17:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is postponed as we encountered issues with some binaries not built for arm64 architecture in our images, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Wednesday October 25 2023, starting at 16:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the mirrorbits service responsible for get.jenkins.io, fallback.get.jenkins.io, mirrors.jenkins.io and mirror.jenkins-ci.org.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] arm64 migration of public nginx ingress on publick8s cluster</title><link>https://status.jenkins.io/issues/2023-10-19-publik8s-public-nginx-ingress-arm64-migration/</link><pubDate>Tue, 10 Oct 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-19-publik8s-public-nginx-ingress-arm64-migration/</guid><category>2023-10-10T12:15:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is now finished, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Thursday October 19 2023, starting at 12:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the publick8s nginx ingress, hosting most of Jenkins Infrastructure public-facing services in order to reduce costs.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Outage on vpn.jenkins.io</title><link>https://status.jenkins.io/issues/2023-10-02-vpn.jenkins.io-outage/</link><pubDate>Mon, 02 Oct 2023 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-02-vpn.jenkins.io-outage/</guid><category>2023-10-02T09:18:00-00:00</category><description>&lt;p&gt;After a hard reboot in azure, we had the VM back.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;An outage is currently happening on vpn.jenkins.io we are investigating.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-09-20-ci.jenkins.io-maintenance/</link><pubDate>Wed, 20 Sep 2023 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-09-20-ci.jenkins.io-maintenance/</guid><category>2023-09-20T14:30:00-00:00</category><description>&lt;p&gt;A maintenance on ci.jenkins.io will be performed with a full service disruption the Wednesday 20 of September 2023 between 11h30 and 14h30 UTC.&lt;/p&gt;</description></item><item><title>[Resolved] weekly.ci.jenkins.io outage</title><link>https://status.jenkins.io/issues/2023-09-13-weekly-ci-outage/</link><pubDate>Wed, 13 Sep 2023 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-09-13-weekly-ci-outage/</guid><category>2023-09-13T13:20:00-00:00</category><description>&lt;p&gt;[Final message]
after a complete recycle of the publick8s nodes the volumes were able to be correctly unmout/mount on the new nodes.&lt;/p&gt;
&lt;p&gt;[Initial message]
weekly.ci service is down &lt;a href="https://weekly.ci.jenkins.io/"&gt;https://weekly.ci.jenkins.io/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Brownout of the Maven Central mirrored repositories in JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2023-09-04-artifactory-central-brownount/</link><pubDate>Mon, 04 Sep 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-09-04-artifactory-central-brownount/</guid><category>2023-09-04T16:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Brownout is finished.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;Monday 04 of September 2023, we&amp;rsquo;ll perform a &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;brownout&lt;/a&gt; operation of 4 hours on the Jenkins Artifactory service at repo.jenkins-ci.org at 10:00 UTC.&lt;/p&gt;
&lt;p&gt;This operation consists in removing all mirrors of the &lt;a href="https://search.maven.org/?eh="&gt;Maven Central&lt;/a&gt; artifact repository from repo.jenkins-ci.org to force Maven builds to download mirrored artefacts from the Maven central instead of our Artifactory instance.&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;planned brownout&lt;/a&gt; is the 2nd tentative related to &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3599"&gt;https://github.com/jenkins-infra/helpdesk/issues/3599&lt;/a&gt; which goal decrease the amount of outbound bandwidth download of our instance.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-09-02-ci.jenkins.io-maintenance/</link><pubDate>Sat, 02 Sep 2023 14:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-09-02-ci.jenkins.io-maintenance/</guid><category>2023-09-02T15:36:00-00:00</category><description>&lt;p&gt;A plugin update to ci.jenkins.io did not complete successfully.
The server is currently reporting that it is restarting.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io, trusted.ci.jenkins.io and cert.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-08-28-cert.ci.jenkins.io-maintenance/</link><pubDate>Mon, 28 Aug 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-28-cert.ci.jenkins.io-maintenance/</guid><category>2023-08-28T15:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is now finished. It took 3h30 instead of the initial 2h due to unexpected disk slowness but was completed successfully.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Monday August 28 2023, starting at 12:00 UTC, the Jenkins controller cert.ci.jenkins.io will be put down for maintenance (migration to a new VM) as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3688"&gt;https://github.com/jenkins-infra/helpdesk/issues/3688&lt;/a&gt;.
Only the Jenkins Security team is impacted.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io, trusted.ci.jenkins.io and cert.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-08-21-trustedci-certci-and-ci-maintenances/</link><pubDate>Mon, 21 Aug 2023 13:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-21-trustedci-certci-and-ci-maintenances/</guid><category>2023-08-21T14:15:00-00:00</category><description>&lt;p&gt;[Final Message]
Operation completed successfully:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Took around 30 minutes as expected.&lt;/li&gt;
&lt;li&gt;A few minor unexpected behaviors are tracked in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3072"&gt;https://github.com/jenkins-infra/helpdesk/issues/3072&lt;/a&gt; (fixed the 22 of October 2023).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
Monday August 21 2023, starting at 13:45 UTC, the Jenkins controllers ci.jenkins.io, trusted.ci.jenkins.io and cert.ci.jenkins.io will be upgraded to use JDK17 instead of JDK11.&lt;/p&gt;
&lt;p&gt;This operation expects 1 or 2 restarts per controller but then should be harmless as we worked on the agent images as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3072"&gt;https://github.com/jenkins-infra/helpdesk/issues/3072&lt;/a&gt; and already upgraded 3 other controllers.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io and trusted.ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-08-17-trustedci-and-ci-maintenances/</link><pubDate>Thu, 17 Aug 2023 17:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-17-trustedci-and-ci-maintenances/</guid><category>2023-08-17T18:00:00-00:00</category><description>&lt;p&gt;Thursday August 17 2023, starting at 16:30 UTC, an infrastructure operation on the &lt;a href="https://ci.jenkins.io"&gt;https://ci.jenkins.io&lt;/a&gt; and &lt;a href="https://trusted.ci.jenkins.io"&gt;https://trusted.ci.jenkins.io&lt;/a&gt; controller will be done.
This operation impacts the network of both services which could lead to network errors when accessing the services and when running build.&lt;/p&gt;
&lt;p&gt;The operation took 1 hour and finished with success.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/azure/pull/454"&gt;https://github.com/jenkins-infra/azure/pull/454&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-08-16-ci-maintenance/</link><pubDate>Wed, 16 Aug 2023 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-16-ci-maintenance/</guid><category>2023-08-16T13:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins and core version.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday August 16 2023, between 11:30 UTC and 13:30 UTC, the &lt;a href="https://ci.jenkins.io"&gt;https://ci.jenkins.io&lt;/a&gt; controller will be unavailable as it will be upgraded and restarted as part of the security advisory announced in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/xOqgDOYxTAw"&gt;https://groups.google.com/g/jenkinsci-advisories/c/xOqgDOYxTAw&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Brownout of the Maven Central mirrored repositories in JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2023-08-02-artifactory-central-brownount/</link><pubDate>Wed, 02 Aug 2023 14:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-02-artifactory-central-brownount/</guid><category>2023-08-02T16:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Brownout is finished after 1h30 (instead of initial 1 hour).&lt;/p&gt;
&lt;p&gt;[Initial Message]
Wednesday 02 of August, we&amp;rsquo;ll perform a &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;brownout&lt;/a&gt; operation of 1 hour on the Jenkins Artifactory service at repo.jenkins-ci.org at 14:30 UTC for ~1 hour.&lt;/p&gt;
&lt;p&gt;This operation consists in removing all mirrors of the &lt;a href="https://search.maven.org/"&gt;Maven Central&lt;/a&gt; artifact repository from repo.jenkins-ci.org to force Maven builds to download mirrored artefacts from the Maven central instead of our Artifactory instance.&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;planned brownout&lt;/a&gt; is a step of &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3599"&gt;https://github.com/jenkins-infra/helpdesk/issues/3599&lt;/a&gt; to decrease the amount of outbound bandwidth download of our instance.&lt;/p&gt;
&lt;p&gt;There should be no functional impact, as Maven as a built-in fallback to the repository &lt;code&gt;central&lt;/code&gt;.
However, we expect the builds on ci.jenkins.io to be a bit slower as the artifacts downloaded from central won&amp;rsquo;t be cached anymore.&lt;/p&gt;</description></item><item><title>[Resolved] reports.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-08-01-reports-migration-within-publick8s/</link><pubDate>Tue, 01 Aug 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-08-01-reports-migration-within-publick8s/</guid><category>2023-08-01T13:15:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well with no disruption.
&lt;a href="https://github.com/jenkins-infra/kubernetes-management/pull/4209"&gt;https://github.com/jenkins-infra/kubernetes-management/pull/4209&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of &lt;a href="https://reports.jenkins.io"&gt;reports.jenkins.io&lt;/a&gt; from an Intel &lt;code&gt;x86_64&lt;/code&gt; node pool to an &lt;code&gt;arm64&lt;/code&gt; on the cluster &lt;code&gt;publick8s&lt;/code&gt; is planned today, Tuesday 1st of August 2023 at 13h00 UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] javadoc.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-07-31-javadoc-migration-within-publick8s/</link><pubDate>Mon, 31 Jul 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-31-javadoc-migration-within-publick8s/</guid><category>2023-07-31T14:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The migration went well with no disruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of &lt;a href="https://javadoc.jenkins.io"&gt;the javadoc website&lt;/a&gt; from an arm nodepool to another on the cluster &lt;code&gt;publick8s&lt;/code&gt; is planned on Monday 31st of July 2023 at 13h00 UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3623#issuecomment-1613504371"&gt;https://github.com/jenkins-infra/helpdesk/issues/3623#issuecomment-1613504371&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-07-26-ci-maintenance/</link><pubDate>Wed, 26 Jul 2023 12:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-26-ci-maintenance/</guid><category>2023-07-26T14:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins and core version.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Wednesday July 26 2023, between 10:30 UTC and 14:30 UTC, the ci.jenkins.io controller will be unavailable as it will be upgraded and restarted as part of the security advisory announced in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/2GiSsACaT28"&gt;https://groups.google.com/g/jenkinsci-advisories/c/2GiSsACaT28&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-07-12-ci-maintenance/</link><pubDate>Wed, 12 Jul 2023 11:38:11 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-12-ci-maintenance/</guid><category>2023-07-12T13:57:00-00:00</category><description>&lt;p&gt;[Final Message]
The ci.jenkins.io controller is running with updated plugins.&lt;/p&gt;
&lt;p&gt;[Initial message]
Wednesday July 12, 2023 the ci.jenkins.io controller will be restarted if plugin updates are needed as a result of the plugin security advisory.&lt;/p&gt;
&lt;p&gt;The restart may happen between 11:30am UTC and 13:30 UTC.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/y50ITBfDesw"&gt;https://groups.google.com/g/jenkinsci-advisories/c/y50ITBfDesw&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update AKS clusters Kubernetes version to 1.25</title><link>https://status.jenkins.io/issues/2023-07-07-maintenance-aks-k8s-1-25/</link><pubDate>Fri, 07 Jul 2023 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-07-maintenance-aks-k8s-1-25/</guid><category>2023-07-07T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished at 15:30 UTC after a full downtime of ~3 hours on the &lt;code&gt;publick8s&lt;/code&gt; cluster due to a network issue.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3582"&gt;https://github.com/jenkins-infra/helpdesk/issues/3582&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
We&amp;rsquo;re doing an AKS clusters upgrade from 1.24 to 1.25 the Friday 07th of July 2023, starting at 08:30 UTC.&lt;/p&gt;
&lt;p&gt;No outage is expected, but there will be application restarts, including a downtime between 3 to 10 minutes for &lt;code&gt;ldap.jenkins.io&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Other services potentially impacted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;previews of *.jenkins.io pull requests (infra.ci.jenkins.io)&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2023-07-06-jira-outage/</link><pubDate>Thu, 06 Jul 2023 21:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-06-jira-outage/</guid><category>2023-07-06T23:57:00-00:00</category><description>&lt;p&gt;[Final message]
&lt;a href="https://groups.google.com/g/jenkinsci-dev/c/Qx4QtAFIdoA/m/dFDi_1ECBwAJ"&gt;This work is completed.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;More details are available from the Linux Foundation in &lt;a href="https://status.linuxfoundation.org/incidents/0618mjh9356n"&gt;Jira upgrade for Jenkins&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to three hours beginning at 9:00 PM (UTC) Thursday July 6, 2023 so that it can be upgraded.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-07-04-ci-maintenance/</link><pubDate>Tue, 04 Jul 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-07-04-ci-maintenance/</guid><category>2023-07-05T09:00:00-00:00</category><description>&lt;p&gt;[Final Message]
Everything is back to normal on ci.jenkins.io. Follows up in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3535"&gt;https://github.com/jenkins-infra/helpdesk/issues/3535&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update 3]
At 21h30 UTC, all builds (except BOM) were able to run, with some runtime errors in some cases due to missing plugins.&lt;/p&gt;
&lt;p&gt;[Update 3]
At 20h45 UTC, the migration was finished and ci.jenkins.io was available again.&lt;/p&gt;
&lt;p&gt;[Update 2]
ci.jenkins.io remains down until 5th of July due to I/O issues on the old &lt;code&gt;JENKINS_HOME&lt;/code&gt;.
Ref. &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3535#issuecomment-1620171502."&gt;https://github.com/jenkins-infra/helpdesk/issues/3535#issuecomment-1620171502.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Update 1]
Kubernetes 1.25 upgrade on AWS went well and was finished at 15:00 UTC.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io is planned the Tuesday 4th of July 2023:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Initial operation starts at 13:00 UTC with an AWS Kubernetes upgrade to 1.25.
&lt;ul&gt;
&lt;li&gt;Expected impact is no BOM build will be possible during the maintenance while other builds executed in DigitalOcean and/or Azure.&lt;/li&gt;
&lt;li&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3582"&gt;https://github.com/jenkins-infra/helpdesk/issues/3582&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Second part of the operation starts at 14h30 UTC for a migration of the virtual machine to a new generation of hardware (Azure VM Gen2) and operating system (Ubuntu 22.04).
&lt;ul&gt;
&lt;li&gt;Expected impact is a full downtime during the migration.&lt;/li&gt;
&lt;li&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3535"&gt;https://github.com/jenkins-infra/helpdesk/issues/3535&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] DigitalOcean outage</title><link>https://status.jenkins.io/issues/2023-06-21-digitalocean-incident/</link><pubDate>Wed, 21 Jun 2023 11:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-21-digitalocean-incident/</guid><category>2023-06-22T16:45:00-00:00</category><description>&lt;p&gt;[Final message]
Incident is reported officially by Digital Ocean and is finished: &lt;a href="https://status.digitalocean.com/incidents/bclmy32d12p0"&gt;https://status.digitalocean.com/incidents/bclmy32d12p0&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve restored all the nominal configuration after health-checking the clusters.&lt;/p&gt;
&lt;p&gt;[Initial message]
DigitalOcean infrastructure is having a network outage.
We see a high rate of TCP errors on both Kubernetes clusters &lt;code&gt;doks&lt;/code&gt; (agents for ci.jenkins.io) and &lt;code&gt;doks-public&lt;/code&gt; (Artifact Caching Proxy for these agents).
We are disabling temporarily agent scheduling in DigitalOcean: all ci.jenkins.io containers workload will run in AWS or Azure instead.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3633"&gt;https://github.com/jenkins-infra/helpdesk/issues/3633&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-06-14-ci-maintenance/</link><pubDate>Wed, 14 Jun 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-14-ci-maintenance/</guid><category>2023-06-14T13:00:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended. Advisory published: &lt;a href="https://www.jenkins.io/security/advisory/2023-06-14/"&gt;https://www.jenkins.io/security/advisory/2023-06-14/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for security advisory. (ref. &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/CD7La5U-dIQ"&gt;https://groups.google.com/g/jenkinsci-advisories/c/CD7La5U-dIQ&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>[Resolved] jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-13-jenkins-io-migration-to-publick8s/</link><pubDate>Tue, 13 Jun 2023 09:25:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-13-jenkins-io-migration-to-publick8s/</guid><category>2023-06-13T10:10:00-00:00</category><description>&lt;p&gt;[Final message]
Migration successfully completed, no service interruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of &lt;a href="https://www.jenkins.io"&gt;Jenkins website&lt;/a&gt; from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned on Tuesday 13th of June 2023 at 12h00 UTC.&lt;/p&gt;
&lt;p&gt;In order to avoid any concurrent updates, jenkins-infra/jenkins.io builds will be disabled for less than an hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1588040182"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1588040182&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] plugins.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-13-plugin-site-migration-to-publick8s/</link><pubDate>Tue, 13 Jun 2023 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-13-plugin-site-migration-to-publick8s/</guid><category>2023-06-13T09:15:00-00:00</category><description>&lt;p&gt;[Final message]
Migration successfully completed, no service interruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of &lt;a href="https://plugins.jenkins.io"&gt;the plugins site website&lt;/a&gt; from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned on Tuesday 13th of June 2023 at 08h00 UTC.&lt;/p&gt;
&lt;p&gt;In order to avoid any concurrent updates, jenkins-infra/plugin-site infra builds will be disabled for less than an hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1588038925"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1588038925&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] plugin-site-issues migration</title><link>https://status.jenkins.io/issues/2023-06-12-plugin-site-issues-migration-to-publick8s/</link><pubDate>Mon, 12 Jun 2023 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-12-plugin-site-issues-migration-to-publick8s/</guid><category>2023-06-12T14:00:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;plugin-site-issue&amp;rdquo; service (&lt;code&gt;plugin-site-issues.jenkins.io&lt;/code&gt; - used by plugins.jenkins.io to retrieve release and issue information about a plugin) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Monday 12st of June 2023 at 13h00 UTC.
While there should not be any interruption, the corresponding service may be down for less than one hour, and plugins.jenkins.io may be impacted.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586972368"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586972368&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] mirrorbits migration</title><link>https://status.jenkins.io/issues/2023-06-12-mirrorbits-migration-to-publick8s/</link><pubDate>Mon, 12 Jun 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-12-mirrorbits-migration-to-publick8s/</guid><category>2023-06-12T13:30:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;mirrorbits&amp;rdquo; service from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Monday 12st of June 2023 at 12h00 UTC.
While there should not be any interruption, the corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on VM agents on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-06-09-ci-outage/</link><pubDate>Fri, 09 Jun 2023 12:37:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-09-ci-outage/</guid><category>2023-06-09T12:42:00-00:00</category><description>&lt;p&gt;[Final message]
revert disabled plugin and restart ci.jenkins.io&lt;/p&gt;
&lt;p&gt;[Initial message]
There is an outage on ci.jenkins.io since 12h35 UTC.
following plugin removal there is a configuration as code error message.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3573#issuecomment-1584503523"&gt;https://github.com/jenkins-infra/helpdesk/issues/3573#issuecomment-1584503523&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Brownout of the 'jgit' mirrored repository in JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2023-06-08-artifactory-operation/</link><pubDate>Thu, 08 Jun 2023 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-08-artifactory-operation/</guid><category>2023-06-08T13:00:00-00:00</category><description>&lt;p&gt;[Final message]
Our experiment is now finished. Projects using the Eclipse &lt;code&gt;jgit&lt;/code&gt; had errors downloading artefacts during the operation but it is back to normal&lt;/p&gt;
&lt;p&gt;[Initial message]
The mirror repository &lt;code&gt;jgit&lt;/code&gt; in the JFrog Artifactory service &amp;lt;repo.jenkins-ci.org&amp;gt; will be restricted to only authenticated users the 8 June 2023 at 12:30UTC for 30 min.&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://en.wikipedia.org/wiki/Brownout_(software_engineering)"&gt;planned brownout&lt;/a&gt; is a step of &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3599"&gt;https://github.com/jenkins-infra/helpdesk/issues/3599&lt;/a&gt; to study the behavior of our builds.&lt;/p&gt;
&lt;p&gt;There should be no impact, as the artifacts should be consumed through the &lt;code&gt;public&lt;/code&gt; virtual repository but we cannot be 100% sure, hence this operation.&lt;/p&gt;</description></item><item><title>[Resolved] ldap.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-08-ldap-migration-to-publick8s/</link><pubDate>Thu, 08 Jun 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-08-ldap-migration-to-publick8s/</guid><category>2023-06-08T13:05:00-00:00</category><description>&lt;p&gt;[Final message]
Although the intended redirections from accounts.jenkins.io &amp;amp; accounts.jenkins-ci.org to status.jenkins.io didn&amp;rsquo;t work as expected, the LDAP migration has been successfully completed, no service interruption.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the LDAP service (&lt;code&gt;ldap.jenkins.io&lt;/code&gt; - used for Jenkins user authentication) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Thursday 8th of June 2023 at 12h00 UTC.&lt;/p&gt;
&lt;p&gt;In order to avoid any user base modification while migrating this service, &lt;a href="https://accounts.jenkins.io"&gt;accounts.jenkins.io&lt;/a&gt; access will be disabled for less than an hour.&lt;/p&gt;
&lt;p&gt;Although no downtime is expected, the following services might be impacted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;JFrog Artifactory (repo.jenkins-ci.org)&lt;/li&gt;
&lt;li&gt;ci.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;trusted.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;vpn.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1576741071"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1576741071&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] ldap outage</title><link>https://status.jenkins.io/issues/2023-06-06-ldap-outage/</link><pubDate>Tue, 06 Jun 2023 12:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-06-ldap-outage/</guid><category>2023-06-06T14:50:00-00:00</category><description>&lt;p&gt;[Final message]
The service has been restored, a misconfiguration was responsible for its outage.&lt;/p&gt;
&lt;p&gt;[Initial message]
ldap service is down so no authentification working on jira or controllers&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io scans outage</title><link>https://status.jenkins.io/issues/2023-06-05-ci-jenkins-io-scans-outage/</link><pubDate>Mon, 05 Jun 2023 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-05-ci-jenkins-io-scans-outage/</guid><category>2023-06-05T23:59:59-00:00</category><description>&lt;p&gt;A change in the GitHub REST API is responsible for a bug in the integration used by Jenkins to retrieve repository maintainers.
Repository scans on &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; fail to retrieve pull requests.&lt;/p&gt;
&lt;p&gt;The issue will require a new release of the &lt;a href="https://github.com/hub4j/github-api/"&gt;GitHub API library&lt;/a&gt; and the &lt;a href="https://plugins.jenkins.io/github-api/"&gt;GitHub API plugin&lt;/a&gt; that packages the library as a Jenkins plugin.
A patched GitHub API has been installed on ci.jenkins.io while waiting for the release of the library and the plugin.&lt;/p&gt;
&lt;p&gt;See the &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3617"&gt;help desk issue&lt;/a&gt; to track progress.&lt;/p&gt;</description></item><item><title>[Resolved] accounts.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-02-accountapp-migration-to-publick8s/</link><pubDate>Fri, 02 Jun 2023 11:25:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-02-accountapp-migration-to-publick8s/</guid><category>2023-06-02T11:50:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;accountapp&amp;rdquo; service (&lt;code&gt;accounts.jenkins.io&lt;/code&gt;) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Friday 2st of June 2023 at 13h00 UTC.
The corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1573486575"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1573486575&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] reports.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-02-reports-migration-to-publick8s/</link><pubDate>Fri, 02 Jun 2023 08:40:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-02-reports-migration-to-publick8s/</guid><category>2023-06-02T11:05:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;Reports&amp;rdquo; application (&lt;code&gt;reports.jenkins.io&lt;/code&gt;) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Friday 2st of June 2023 at 08h45 UTC.
The corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1573354662"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1573354662&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] trusted.ci.jenkins.io migration to Azure</title><link>https://status.jenkins.io/issues/2023-06-02-trusted.ci-migration-to-azure/</link><pubDate>Fri, 02 Jun 2023 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-02-trusted.ci-migration-to-azure/</guid><category>2023-06-02T05:00:00-00:00</category><description>&lt;p&gt;[Final message]
The migration was finished at 17h00 UTC and everything looks good: Update Center, RPU, jenkins.io and all jobs are successful.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;Trusted&amp;rdquo; controller (&lt;code&gt;trusted.ci.jenkins.io&lt;/code&gt;) virtual machines from AWS EC2 to Azure is planned today on Friday 2 of June 2023 starting at 08h30 UTC.
The service will be down until the migration is complete and finished.&lt;/p&gt;
&lt;p&gt;It has an impact on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The Update Center (&lt;code&gt;updates.jenkins.io&lt;/code&gt;): any release of a plugin won&amp;rsquo;t be visible until the end of the migration&lt;/li&gt;
&lt;li&gt;The CD plugin process: the Repository Permission Updater system won&amp;rsquo;t be updated until the end of the migration: Publishing a new plugin with the CD process or logging-in to Artifactory (repo.jenkins-ci.org) could be impacted&lt;/li&gt;
&lt;li&gt;The Plugin site (&lt;code&gt;plugins.jenkins.io&lt;/code&gt;) and the Javadoc (&lt;code&gt;javadoc.jenkins.io&lt;/code&gt;) won&amp;rsquo;t be updated during the migration&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3486"&gt;https://github.com/jenkins-infra/helpdesk/issues/3486&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] uplink.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-06-01-uplink-migration/</link><pubDate>Thu, 01 Jun 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-01-uplink-migration/</guid><category>2023-06-01T17:00:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;Uplink&amp;rdquo; application (&lt;code&gt;uplink.jenkins.io&lt;/code&gt; - used for telemetry) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Thursday 1st of June 2023 at 12h45 UTC.
The corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &amp;lt;&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1571588945"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1568499546&lt;/a&gt;&amp;gt;.&lt;/p&gt;</description></item><item><title>[Resolved] rating.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-05-30-rating-migration/</link><pubDate>Tue, 30 May 2023 16:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-05-30-rating-migration/</guid><category>2023-05-30T17:15:00-00:00</category><description>&lt;p&gt;[Final message]
Migration complete with a 3 minutes downtime.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the application &amp;ldquo;Rating&amp;rdquo; (&lt;code&gt;rating.jenkins.io&lt;/code&gt; - used by &lt;a href="https://www.jenkins.io/changelog-stable/"&gt;https://www.jenkins.io/changelog-stable/&lt;/a&gt; and &lt;a href="https://www.jenkins.io/changelog/"&gt;https://www.jenkins.io/changelog/&lt;/a&gt; pages) from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Tuesday 30th of May 2023 at 16h45 UTC.
The corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1568499546"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1568499546&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Incremental Publisher migration</title><link>https://status.jenkins.io/issues/2023-05-26-incrementals-publisher-migration/</link><pubDate>Fri, 26 May 2023 16:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-05-26-incrementals-publisher-migration/</guid><category>2023-05-26T17:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;Migration completed with no disruption&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the Incremental Publisher (&lt;code&gt;incrementals-publisher.jenkins.io&lt;/code&gt;) application from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Friday 26th of May 2023 at 16h15 UTC.&lt;/p&gt;
&lt;p&gt;No downtime is expected as the service is stateless but slowness might happen.&lt;/p&gt;
&lt;p&gt;More information in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564632990"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564632990&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Plugins Health Score migration</title><link>https://status.jenkins.io/issues/2023-05-26-publicheathscore-migration/</link><pubDate>Fri, 26 May 2023 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-05-26-publicheathscore-migration/</guid><category>2023-05-26T14:35:00-00:00</category><description>&lt;p&gt;[Final message]
Migration done without downtime on plugins.jenkins.io and only 10mn plugin-health.jenkins.io.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the application Plugins Health Score from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Friday 26th of May 2023 at 13h30 UTC, the corresponding services may be down for less than one hour:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564517009"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564517009&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-05-16-ci-maintenance/</link><pubDate>Tue, 16 May 2023 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-05-16-ci-maintenance/</guid><category>2023-05-16T13:00:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for security advisory. (ref. &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/_mJEHe9lXTU"&gt;https://groups.google.com/g/jenkinsci-advisories/c/_mJEHe9lXTU&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>[Resolved] Outage for container agents on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-04-25-ci-agents-outage/</link><pubDate>Tue, 25 Apr 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-04-25-ci-agents-outage/</guid><category>2023-04-26T14:02:00-00:00</category><description>&lt;p&gt;[Final Message]
A new cluster was created and used to replace the former one, with additional measures to avoid future lock out.
Follow up in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3542"&gt;https://github.com/jenkins-infra/helpdesk/issues/3542&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Updated]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Root cause found: the problem was caused by a mix of technical and human errors which led to a lockout of the AWS EKS cluster used by ci.jenkins.io.&lt;/li&gt;
&lt;li&gt;The cluster requires a re-creation, which can take 1 to 2 hours.&lt;/li&gt;
&lt;li&gt;A remediation was applied: DigitalOcean is now used for container workload until the operation is finished: &lt;a href="https://github.com/jenkins-infra/jenkins-infra/commit/2bfbb53123b43317d91a280ce8b8c9ae4c8b35a2"&gt;https://github.com/jenkins-infra/jenkins-infra/commit/2bfbb53123b43317d91a280ce8b8c9ae4c8b35a2&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial message]
ci.jenkins.io is not able to start container agents.&lt;/p&gt;
&lt;p&gt;The builds requiring a container agents are queued, while the other are executed as usual.&lt;/p&gt;</description></item><item><title>[Resolved] Incident on get.jenkins.io (Mirror Redirector)</title><link>https://status.jenkins.io/issues/2023-04-19-get.jenkins.io-incident/</link><pubDate>Wed, 19 Apr 2023 07:32:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-04-19-get.jenkins.io-incident/</guid><category>2023-04-19T13:25:00-00:00</category><description>&lt;p&gt;[Update]
Triggering a node pool image OS upgrade to recycle volume mounts. Expect a 4-5 minutes outage on the LDAP connection (e.g. authentication on issues.jenkins.io and (.*)ci.jenkins.io)&lt;/p&gt;
&lt;p&gt;[Initial message]
The mirror redirector service (get.jenkins.io) is slow and may responds HTTP/502 errors on some requests as reported by a user at 7:32am UTC - &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3525"&gt;https://github.com/jenkins-infra/helpdesk/issues/3525&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Investigation in progress, this page will be updated accordingly to our findings.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-04-12-ci-maintenance/</link><pubDate>Wed, 12 Apr 2023 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-04-12-ci-maintenance/</guid><category>2023-04-12T15:50:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for security advisory. (ref. &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/ccmIF1Vs-9A"&gt;https://groups.google.com/g/jenkinsci-advisories/c/ccmIF1Vs-9A&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>[Resolved] Outage on VM agents on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-03-28-ci-outage/</link><pubDate>Tue, 28 Mar 2023 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-28-ci-outage/</guid><category>2023-03-29T15:55:00-00:00</category><description>&lt;p&gt;[Final message]
Outage finished, cleanup operations were done the 30 March with no impact.&lt;/p&gt;
&lt;p&gt;[Update - 2023-03-29 15h50 UTC]
Build queue cleaned-up two times, and reloaded the state from file system. The instance ssems back to &amp;ldquo;normal&amp;rdquo;. Watching it.&lt;/p&gt;
&lt;p&gt;[Update - 2023-03-29 15h30 UTC]
Build queue did not decreased, the instance is unresponsive: proceeding to purge the queue to regain control, as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3474#issuecomment-1488838514"&gt;https://github.com/jenkins-infra/helpdesk/issues/3474#issuecomment-1488838514&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Update - 2023-03-29 14h00 UTC]
Increased the Azure VM capacity to 80 (instead 10 or 20) for each kind (Linux, Windows, etc.) of template&lt;/p&gt;
&lt;p&gt;[Update - 2023-03-29 07h30 UTC]
The build queue is still full (around 1600 build waiting). Caused by &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3474"&gt;https://github.com/jenkins-infra/helpdesk/issues/3474&lt;/a&gt; (organization scanning trigger).&lt;/p&gt;
&lt;p&gt;[Update - 2023-03-28 21h00 UTC]
The Azure VM agents are working as expected and started treating builds&lt;/p&gt;
&lt;p&gt;[Initial message]
There is an outage on ci.jenkins.io since 14h00 UTC.
Build requiring a virtual machine are being queued.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3459#issuecomment-1487228241"&gt;https://github.com/jenkins-infra/helpdesk/issues/3459#issuecomment-1487228241&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Jenkins 2.397 and 2.387.2: New Linux Repository Signing Keys</title><link>https://status.jenkins.io/issues/2023-03-28-new-signing-key/</link><pubDate>Tue, 28 Mar 2023 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-28-new-signing-key/</guid><category>2023-04-05T14:20:00-00:00</category><description>&lt;p&gt;Beginning March 28, 2023, the Jenkins weekly releases will use new repository signing keys for the Linux installation packages.
The same change will be made in Jenkins LTS releases beginning April 5, 2023.
Administrators of Linux systems &lt;em&gt;must&lt;/em&gt; install the new signing keys on their Linux servers &lt;em&gt;before&lt;/em&gt; installing Jenkins Jenkins weekly 2.397 or Jenkins LTS 2.387.2.&lt;/p&gt;
&lt;p&gt;More details and instructions at &lt;a href="https://www.jenkins.io/blog/2023/03/27/repository-signing-keys-changing/"&gt;https://www.jenkins.io/blog/2023/03/27/repository-signing-keys-changing/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] release.ci.jenkins.io migration</title><link>https://status.jenkins.io/issues/2023-03-23-release-ci-migration/</link><pubDate>Thu, 23 Mar 2023 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-23-release-ci-migration/</guid><category>2023-03-27T10:20:00-00:00</category><description>&lt;p&gt;[Final message]
The migration is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll migrate release.ci.jenkins.io to a new private cluster for a better segregation of release jobs, and easier maintenance as this new cluster and related resources are managed as code.&lt;/p&gt;
&lt;p&gt;This migration will start today Thursday 23th of May at 15h00 UTC. Most of the work has been done in a preliminary phase, it should take two to three hours to finish the migration, with a total unavailability of release.ci.jenkins.io until it&amp;rsquo;s done.&lt;/p&gt;
&lt;p&gt;Important notice: every person needing to work on the next releases will need access to the new private VPN before next Tuesday, as the existing VPN doesn&amp;rsquo;t allow access to this new cluster and thus the next location of release.ci.jenkins.io.
We&amp;rsquo;ll send further instructions for this by email.&lt;/p&gt;
&lt;p&gt;More information and detailed migration plan: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1463863691"&gt;https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1463863691&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-03-21-ci-maintenance/</link><pubDate>Tue, 21 Mar 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-21-ci-maintenance/</guid><category>2023-03-21T14:20:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for security advisory. (ref. &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/RmkqB1wAY14"&gt;https://groups.google.com/g/jenkinsci-advisories/c/RmkqB1wAY14&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-03-17-maintenance-window-ci/</link><pubDate>Fri, 17 Mar 2023 18:27:45 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-17-maintenance-window-ci/</guid><category>2023-03-17T19:07:41-00:00</category><description>&lt;p&gt;Maintenance of ci.jenkins.io by the infrastructure team.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2023-03-11-jira-outage/</link><pubDate>Sat, 11 Mar 2023 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-11-jira-outage/</guid><category>2023-03-11T00:22:00-00:00</category><description>&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, will be down for up to 30 minutes beginning at midnight (UTC) Saturday March 11, 2023 so that it can be upgraded.&lt;/p&gt;</description></item><item><title>[Resolved] Bots migration</title><link>https://status.jenkins.io/issues/2023-03-09-bots-migrations/</link><pubDate>Thu, 09 Mar 2023 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-09-bots-migrations/</guid><category>2023-03-09T10:55:00-00:00</category><description>&lt;p&gt;[Final message]
The 3 services are back online and working as intended on their new cluster.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the bots from prodpublick8s cluster to privatek8s cluster is planned on Thursday 9th of March 2023 at 9h00 UTC, the corresponding services will be down for less than one hour:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;jenkins-admin IRC bot (#jenkins-hosting channel on IRC)&lt;/li&gt;
&lt;li&gt;github-comment-ops, reacting to comments on GitHub&lt;/li&gt;
&lt;li&gt;rss2twitter bot (&lt;a href="https://twitter.com/jenkins_release"&gt;https://twitter.com/jenkins_release&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1460023896"&gt;https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1460023896&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-03-08-ci-maintenance/</link><pubDate>Wed, 08 Mar 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-08-ci-maintenance/</guid><category>2023-03-08T14:10:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for security advisory (ref. &lt;a href="https://groups.google.com/g/jenkinsci-advisories/c/RmkqB1wAY14"&gt;https://groups.google.com/g/jenkinsci-advisories/c/RmkqB1wAY14&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>[Resolved] Update Azure Service Principal credential for the AKS cluster prodpublick8s</title><link>https://status.jenkins.io/issues/2023-03-07-maintenance-prodpublick8s-sp/</link><pubDate>Tue, 07 Mar 2023 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-03-07-maintenance-prodpublick8s-sp/</guid><category>2023-03-07T13:30:00-00:00</category><description>&lt;p&gt;[Closing]
The operation went well and took 30 minutes, including 5 minute of restart for ldap.jenkins.io.&lt;/p&gt;
&lt;p&gt;[Opening]
We&amp;rsquo;ll perform an operation on the AKS cluster &lt;code&gt;prodpublick8s&lt;/code&gt; the 07 of March 2023 at 13:00 UTC.&lt;/p&gt;
&lt;p&gt;The goal of this operation is to rotate the (soon-to-be-expired) Azure Service Principal credential for this cluster.&lt;/p&gt;
&lt;p&gt;This operation will restart all the machines of the cluster.&lt;/p&gt;
&lt;p&gt;The following services will be restarted (e.g. unavailable during the restart phase):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io (⚠️ authentication on ci.jenkins.io, issues.jenkins.io and repo.jenkins-ci.org is affected)&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The following services will be migrated without downtime (but slower response time during the operation):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3433"&gt;https://github.com/jenkins-infra/helpdesk/issues/3433&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update AKS clusters Kubernetes version to 1.24</title><link>https://status.jenkins.io/issues/2023-02-23-maintenance-aks-k8s-1-24/</link><pubDate>Thu, 23 Feb 2023 10:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-02-23-maintenance-aks-k8s-1-24/</guid><category>2023-02-22T15:00:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re doing an AKS clusters upgrade from 1.23 to 1.24 today, Thursday 23th of February 2023, starting at 10:30 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3387"&gt;https://github.com/jenkins-infra/helpdesk/issues/3387&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact on the Azure artifact caching proxy.
In the case it&amp;rsquo;s not responding, the builds will simply fallback to repo.jenkins-ci.org to retrieve artifacts.&lt;/p&gt;
&lt;p&gt;Other services potentially impacted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;previews of *.jenkins.io pull requests (infra.ci.jenkins.io)&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Update EKS Kubernetes version to 1.24</title><link>https://status.jenkins.io/issues/2023-02-22-maintenance-eks-k8s-1-24/</link><pubDate>Wed, 22 Feb 2023 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-02-22-maintenance-eks-k8s-1-24/</guid><category>2023-02-22T17:30:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re doing an EKS clusters upgrade from 1.23 to 1.24 this afternoon, Wednesday 22th of February 2023, starting at 14:00 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3387"&gt;https://github.com/jenkins-infra/helpdesk/issues/3387&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact on the building queue for ci.jenkins.io even with the DOKS cluster to take the load.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-02-15-ci-maintenance/</link><pubDate>Wed, 15 Feb 2023 11:55:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-02-15-ci-maintenance/</guid><category>2023-02-15T12:55:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended.&lt;/p&gt;
&lt;p&gt;[Initial message]
Maintenance on ci.jenkins.io, down for plugin security advisory.&lt;/p&gt;</description></item><item><title>[Resolved] s390x agent restart on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-02-03-s390x-agent-down/</link><pubDate>Fri, 03 Feb 2023 16:00:00 -0500</pubDate><guid>https://status.jenkins.io/issues/2023-02-03-s390x-agent-down/</guid><category>2023-02-03T22:00:00-05:00</category><description>&lt;p&gt;The IBM System 390 agent connected to ci.jenkins.io may be restarted during a maintenance window Friday 3 Feb 2023 from 4pm to 10pm ET.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on jenkins.io</title><link>https://status.jenkins.io/issues/2023-01-25-network-outage/</link><pubDate>Wed, 25 Jan 2023 09:10:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-01-25-network-outage/</guid><category>2023-01-25T09:35:00-00:00</category><description>&lt;p&gt;[Final message]
We manually tested and purged the fastly cache and saw the errors (on team members affected networks) disappearing.&lt;/p&gt;
&lt;p&gt;As not all users where impacted, we think it&amp;rsquo;s an incident on fastly side : &lt;a href="https://www.fastlystatus.com/incident/375724"&gt;https://www.fastlystatus.com/incident/375724&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial message]
The &lt;a href="https://www.jenkins.io/doc/developer/security/scan/"&gt;jenkins.io&lt;/a&gt; website responds with HTTP/503 errors for some users and some pages (but not all).&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2023-01-24-ci-down/</link><pubDate>Tue, 24 Jan 2023 12:33:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-01-24-ci-down/</guid><category>2023-01-24T15:20:33-00:00</category><description>&lt;p&gt;Updates for plugin security advisory.&lt;/p&gt;</description></item><item><title>[Resolved] PostgreSQL maintenance</title><link>https://status.jenkins.io/issues/2023-01-20-postgresql-maintenance/</link><pubDate>Fri, 20 Jan 2023 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-01-20-postgresql-maintenance/</guid><category>2023-01-20T17:30:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re working on moving the PostgreSQL database to a new virtual network following infra.ci.jenkins.io cluster migration. There might be some services interruption.&lt;/p&gt;</description></item><item><title>[Resolved] infra.ci.jenkins.io cluster migration</title><link>https://status.jenkins.io/issues/2023-01-19-infra-ci-migration/</link><pubDate>Thu, 19 Jan 2023 15:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-01-19-infra-ci-migration/</guid><category>2023-01-19T18:00:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed, everything is back to normal.&lt;/p&gt;
&lt;p&gt;For users wanting to access infra.ci.jenkins.io, you have to add a new OpenVPN configuration like the one detailed in &lt;a href="https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access"&gt;https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access&lt;/a&gt;, but with private.vpn.jenkins.io as remote address instead of vpn.jenkins.io&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve got any problem, please open an help desk issue at &lt;a href="https://github.com/jenkins-infra/helpdesk/"&gt;https://github.com/jenkins-infra/helpdesk/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial message]
In order to migrate infra.ci.jenkins.io to its new cluster (see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2844)"&gt;https://github.com/jenkins-infra/helpdesk/issues/2844)&lt;/a&gt;, we&amp;rsquo;ll need to shut down this instance.&lt;/p&gt;
&lt;p&gt;Apart from infra.ci.jenkins.io jobs concerning jenkins-infra repositories, jenkins.io preview deployments will also be impacted.&lt;/p&gt;
&lt;p&gt;Expected downtime: 1 hour&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-12-27-ci-restarting/</link><pubDate>Tue, 27 Dec 2022 13:32:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-12-27-ci-restarting/</guid><category>2022-12-27T13:38:00-00:00</category><description>&lt;p&gt;Stopping a large scale job &lt;a href="https://ci.jenkins.io/job/Tools/job/bom/job/PR-1625/"&gt;BOM PR-1625&lt;/a&gt; was not ending the jobs and was not deleting agents.
Restarted to release the jobs and delete the more than 150 agents that have been idling for 20 hours.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance with downtime of JFrog Artifactory (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-12-09-artifactory-maintenance/</link><pubDate>Sun, 18 Dec 2022 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-12-09-artifactory-maintenance/</guid><category>2022-12-18T14:30:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance has been completed with success by JFrog.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://repo.jenkins-ci.org"&gt;repo.jenkins-ci.org&lt;/a&gt; is back online, we resumed &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; and &lt;a href="https://trusted.ci.jenkins.io"&gt;trusted.ci.jenkins.io&lt;/a&gt; builds.&lt;/p&gt;
&lt;p&gt;[Initial message]
December 18, 2022 at 09:00am UTC: our sponsor JFrog will proceed to perform maintenance of our &amp;ldquo;jenkinsci&amp;rdquo; Artifactory instance.&lt;/p&gt;
&lt;p&gt;Expect a complete downtime of 1 to 6 hours due to the nature of this maintenance. The maintenance involves cloud migration from Google Cloud to Amazon Web Services.&lt;/p&gt;
&lt;p&gt;Only Jenkins contributors will be impacted, as no releases or builds on ci.jenkins.io or on developer machines will succeed during the downtime.
Jenkins users won’t be impacted.&lt;/p&gt;
&lt;p&gt;Please note that &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; will be in &amp;ldquo;maintenance mode&amp;rdquo; during the operation:
new incoming builds will stay in the build queue while the maintenance mode is enabled, to ensure that no build is lost.&lt;/p&gt;
&lt;p&gt;More information in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3288"&gt;https://github.com/jenkins-infra/helpdesk/issues/3288&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-12-13-ci-down/</link><pubDate>Tue, 13 Dec 2022 10:16:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-12-13-ci-down/</guid><category>2022-12-13T10:31:00-00:00</category><description>&lt;p&gt;[End of outage message]
service is back, analysing logs&lt;/p&gt;
&lt;p&gt;[Initial message]
ci.jenkins.io is not responding&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-11-15-ci-maintenance/</link><pubDate>Tue, 15 Nov 2022 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-11-15-ci-maintenance/</guid><category>2022-11-15T17:20:00-00:00</category><description>&lt;p&gt;[Final message]&lt;br&gt;
The maintenance is ended, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;br&gt;
A maintenance on ci.jenkins.io has been started.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of keycloak bdd</title><link>https://status.jenkins.io/issues/2022-11-09-keycloak-maintenance/</link><pubDate>Wed, 09 Nov 2022 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-11-09-keycloak-maintenance/</guid><category>2022-11-09T16:00:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended, admin faster.&lt;/p&gt;
&lt;p&gt;[Initial message]
A bdd migration is planned the 9 of November at 15:00 UTC.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-11-02-ci.j-maintenance/</link><pubDate>Wed, 02 Nov 2022 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-11-02-ci.j-maintenance/</guid><category>2022-11-02T12:00:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]
A maintenance on ci.jenkins.io is planned the 2 of November at 10:00 UTC.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-11-01-ci.j-maintenance/</link><pubDate>Tue, 01 Nov 2022 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-11-01-ci.j-maintenance/</guid><category>2022-11-01T15:00:00-00:00</category><description>&lt;p&gt;[Final message]
The maintenance is ended, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]
A maintenance on ci.jenkins.io is planned the 1st of November at 13:00 UTC.&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2022-10-26-maintenance-aks-k8s/</link><pubDate>Thu, 27 Oct 2022 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-10-26-maintenance-aks-k8s/</guid><category>2022-10-27T09:00:00-00:00</category><description>&lt;p&gt;[close]
Upgrade done, no issue or problems to report.
see more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3053"&gt;https://github.com/jenkins-infra/helpdesk/issues/3053&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[open]
We&amp;rsquo;ll do an AKS clusters upgrade from 1.22 to 1.23 this Thursday, 27th of October 2022, starting at 08:00 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3053"&gt;https://github.com/jenkins-infra/helpdesk/issues/3053&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] AKS tempprivatek8s version update</title><link>https://status.jenkins.io/issues/2022-10-26-maintenance-aks-tempprivatek8s/</link><pubDate>Wed, 26 Oct 2022 14:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-10-26-maintenance-aks-tempprivatek8s/</guid><category>2022-10-26T15:30:00-00:00</category><description>&lt;p&gt;[close issue]
Private K8S Upgraded without any problems to kubernetes 1.23.&lt;/p&gt;
&lt;p&gt;[open issue]
-We&amp;rsquo;ll do an AKS clusters upgrade from 1.22 to 1.23 this Wednesday, 26th of October 2022, starting at 14:50 UTC.&lt;/p&gt;
&lt;p&gt;-See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3053"&gt;https://github.com/jenkins-infra/helpdesk/issues/3053&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;we expect the following service to get restarted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] EKS Kubernetes version update to 1.23</title><link>https://status.jenkins.io/issues/2022-10-24-maintenance-eks-k8s-1-23/</link><pubDate>Mon, 24 Oct 2022 12:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-10-24-maintenance-eks-k8s-1-23/</guid><category>2022-10-24T16:00:00-00:00</category><description>&lt;p&gt;EKS upgraded to 1.23, eks and eks-public&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3053"&gt;https://github.com/jenkins-infra/helpdesk/issues/3053&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-10-19-ci.j-maintenance/</link><pubDate>Wed, 19 Oct 2022 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-10-19-ci.j-maintenance/</guid><category>2022-10-19T15:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;br&gt;
The maintenance is ended, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;br&gt;
A maintenance on ci.jenkins.io has been started.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2022-09-02-jira-outage/</link><pubDate>Fri, 02 Sep 2022 19:33:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-09-02-jira-outage/</guid><category>2022-09-02T21:33:00-00:00</category><description>&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, is currently down.&lt;/p&gt;
&lt;p&gt;Issue IT-24484 has been raised with the Linux Foundation.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on vpn.jenkins.io</title><link>https://status.jenkins.io/issues/2022-08-30-vpn-outage/</link><pubDate>Tue, 30 Aug 2022 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-08-30-vpn-outage/</guid><category>2022-08-30T08:30:00-00:00</category><description>&lt;p&gt;[Final message]
VPN is back&lt;/p&gt;
&lt;p&gt;[Initial message]
An outage is currently occuring on vpn.jenkins.io we are investigating.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-08-23-ci-maintenance/</link><pubDate>Tue, 23 Aug 2022 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-08-23-ci-maintenance/</guid><category>2022-08-23T12:00:00-00:00</category><description>&lt;p&gt;[Final message] The maintenance is finished, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]
A maintenance on ci.jenkins.io has been started.&lt;/p&gt;</description></item><item><title>[Resolved] Kubernetes Maintenance: Nginx Ingress + Falco upgrades</title><link>https://status.jenkins.io/issues/2022-08-09-maintenance-ingress/</link><pubDate>Tue, 09 Aug 2022 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-08-09-maintenance-ingress/</guid><category>2022-08-09T10:30:00-00:00</category><description>&lt;p&gt;The two main Kubernetes clusters (&lt;code&gt;prodpublick8s&lt;/code&gt; and &lt;code&gt;temp-privatek8s&lt;/code&gt;) of the Jenkins infrastructure are going under maintenance mode to upgrade their nginx ingress and Falco controllers.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Nginx Ingress Controller: &lt;a href="https://github.com/jenkins-infra/kubernetes-management/pull/2591"&gt;https://github.com/jenkins-infra/kubernetes-management/pull/2591&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Falco Controller: &lt;a href="https://github.com/jenkins-infra/kubernetes-management/pull/2596"&gt;https://github.com/jenkins-infra/kubernetes-management/pull/2596&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;While no major down time is expected, the following services could be restarted leading to a 1 to 5 minute disruption:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;fallback.get.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;mirror.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;archives.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;admin.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;grafana.publick8s.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Maintenance on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-07-27-ci-maintenance/</link><pubDate>Wed, 27 Jul 2022 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-07-27-ci-maintenance/</guid><category>2022-07-27T12:35:00-00:00</category><description>&lt;p&gt;[Final message]&lt;br&gt;
The maintenance is finished, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;br&gt;
A maintenance on ci.jenkins.io has been started.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-07-06-ci-maintenance/</link><pubDate>Wed, 06 Jul 2022 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-07-06-ci-maintenance/</guid><category>2022-07-06T18:00:00-00:00</category><description>&lt;p&gt;[Initial message]
The Jenkins Infra. team is going to perform a set of maintenances on ci.jenkins.io as part of
&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3031"&gt;https://github.com/jenkins-infra/helpdesk/issues/3031&lt;/a&gt;,
&lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2984"&gt;https://github.com/jenkins-infra/helpdesk/issues/2984&lt;/a&gt;,
and &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2961"&gt;https://github.com/jenkins-infra/helpdesk/issues/2961&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;These actions require multiple controller restart: that should either queue, cancel or fail the running builds.&lt;/p&gt;</description></item><item><title>[Resolved] JFrog's Artifactory high response time (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-07-04-artifactory-slow/</link><pubDate>Mon, 04 Jul 2022 06:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-07-04-artifactory-slow/</guid><category>2022-07-04T09:26:00-00:00</category><description>&lt;p&gt;[Closing message]
The system went back to normal response time without any action on our side. Monitoring confirmed that it had behaved correctly the 24h hours following the incident.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Our monitoring alerted us that the response time from repo.jenkins-ci.org is highly unusual: from 5 to 8s (instead of 0.5 to 1s).
All contributors of Jenkins are impacted by this slowness, either when downloading dependencies on their machines, or when executing builds on ci.jenkins.io.&lt;/p&gt;
&lt;p&gt;JFrog was alerted, we are waiting for any feedback from them.&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2022-06-28-maintenance-aks-k8s/</link><pubDate>Thu, 30 Jun 2022 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-06-28-maintenance-aks-k8s/</guid><category>2022-06-30T11:30:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;ll do an AKS clusters upgrade from 1.21 to 1.22 this Thursday, 30th of June 2022, starting at 07:00 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2930"&gt;https://github.com/jenkins-infra/helpdesk/issues/2930&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-06-22-ci-maintenance/</link><pubDate>Wed, 22 Jun 2022 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-06-22-ci-maintenance/</guid><category>2022-06-22T13:45:00-00:00</category><description>&lt;p&gt;[Final message] The maintenance is finished, ci.jenkins.io is back online.&lt;/p&gt;
&lt;p&gt;[Initial message]
A maintenance on ci.jenkins.io has been started.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center certificate issue (updates.jenkins.io)</title><link>https://status.jenkins.io/issues/2022-06-16-update-center-certificate-expired/</link><pubDate>Tue, 14 Jun 2022 12:42:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-06-16-update-center-certificate-expired/</guid><category>2022-06-16T13:20:00-00:00</category><description>&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;There is an issue with the Update Center certificate, resulting in this error message in Jenkins instances:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://user-images.githubusercontent.com/21194782/174035222-de83829c-36bb-4015-acd5-8504b3c5c7b8.png" alt="image"&gt;&lt;/p&gt;
&lt;p&gt;It seems plugin updates still work.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re working on it, you can follow the issue here: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2950"&gt;https://github.com/jenkins-infra/helpdesk/issues/2950&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] JFrog's Artifactory slow (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-06-13-repo-slow/</link><pubDate>Mon, 13 Jun 2022 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-06-13-repo-slow/</guid><category>2022-05-15T11:00:00-00:00</category><description>&lt;p&gt;[Final message]
Our JFrog&amp;rsquo;s Artifactory instance is hosted in Google cloud provider, located in region: GCP Us East, it seems that the behavior we have encountered was due to the service disruption google experienced 3 days ago.&lt;/p&gt;
&lt;p&gt;For additional information, you may refer to the corresponding &lt;a href="https://status.cloud.google.com/incidents/Q9MUHCFVpqouJbGrzneJ"&gt;Google Cloud status page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We were alerted by datadog that the JFrog&amp;rsquo;s Artifactory service at &lt;a href="https://repo.jenkins-ci.org"&gt;https://repo.jenkins-ci.org&lt;/a&gt; is slow.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center not updated with new released plugins</title><link>https://status.jenkins.io/issues/2022-05-31-update-centernot-updated/</link><pubDate>Tue, 31 May 2022 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-31-update-centernot-updated/</guid><category>2022-06-01T09:47:00-00:00</category><description>&lt;p&gt;[Close Issue]
the new certificate had been issued and stored within the trusted controller. Both the crawler and the update-center jobs run smoothly again since 07:34am UTC.&lt;/p&gt;
&lt;p&gt;The plugin &amp;ldquo;gap&amp;rdquo; was filled at 09:47am UTC as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2950#issuecomment-1143374848"&gt;https://github.com/jenkins-infra/helpdesk/issues/2950#issuecomment-1143374848&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Open Issue]
The service updates.jenkins.io, which provides a catalog of the jenkins plugins, is not updated since the 31th of May 2022, around noon UTC.
It is caused by a safety measure that forbid updates of the catalog: the signing certificate expires soon and must be renewed.
More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2950"&gt;https://github.com/jenkins-infra/helpdesk/issues/2950&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Update Center (updates.jenkins.io) flaky, slow with timeouts</title><link>https://status.jenkins.io/issues/2022-05-28-updates-flaky/</link><pubDate>Sat, 28 May 2022 02:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-28-updates-flaky/</guid><category>2022-05-30T11:00:00-00:00</category><description>&lt;p&gt;[close issue]
We were able to fix the configuration of the service to a fine tuned value. Closing the incident after 24 hours without issues.&lt;/p&gt;
&lt;p&gt;[edit]
Issue to track changes: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2960"&gt;https://github.com/jenkins-infra/helpdesk/issues/2960&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Open Issue]
The service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; is experimenting flakiness with a lot of HTTP timeouts.
We are searching the source of trouble and we&amp;rsquo;ll keep you informed.&lt;/p&gt;</description></item><item><title>[Resolved] Debian package installs unavailable</title><link>https://status.jenkins.io/issues/2022-05-28-debian-installs-broken/</link><pubDate>Fri, 27 May 2022 16:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-28-debian-installs-broken/</guid><category>2022-05-29T16:22:00-00:00</category><description>&lt;p&gt;[Close Issue]
A combination of external contributor fixes (HTTPS redirection) and configuration fix (rollback to the correct GPG key) fixed the issues.
Closing as confirmed by 3 different users (on GitHub and IRC).&lt;/p&gt;
&lt;p&gt;[edit]
Details and follow up on the following GitHub issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2957"&gt;https://github.com/jenkins-infra/helpdesk/issues/2957&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Open Issue]
The Debian package installer fails to install from &lt;a href="https://pkg.jenkins.io"&gt;pkg.jenkins.io&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The failure message is:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-console" data-lang="console"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Err:2 https://pkg.jenkins.io/debian binary/ jenkins 2.349
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Redirection from https to &amp;#39;http://mirrors.jenkins.io/debian/jenkins_2.349_all.deb&amp;#39; is forbidden [IP: 146.75.34.133 443]
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Fetched 248 kB in 0s (2256 kB/s)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;E: Failed to fetch https://pkg.jenkins.io/debian/binary/jenkins_2.349_all.deb
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;A workaround is available by downloading the &lt;a href="https://get.jenkins.io/debian/"&gt;weekly installer&lt;/a&gt; or the &lt;a href="https://get.jenkins.io/debian-stable/"&gt;LTS installer&lt;/a&gt; from get.jenkins.io and then installing it with dpkg.&lt;/p&gt;
&lt;h3 id="lts-workaround"&gt;LTS workaround&lt;/h3&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-console" data-lang="console"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# wget https://get.jenkins.io/debian-stable/jenkins_2.332.3_all.deb
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# dpkg -i jenkins_2.332.3_all.deb
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="weekly-workaround"&gt;Weekly workaround&lt;/h3&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-console" data-lang="console"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# wget https://get.jenkins.io/debian/jenkins_2.349_all.deb
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# dpkg -i jenkins_2.349_all.deb
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description></item><item><title>[Resolved] pkg.jenkins.io SSL certificate expired</title><link>https://status.jenkins.io/issues/2022-05-27-ssl-certificate-expired/</link><pubDate>Fri, 27 May 2022 16:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-27-ssl-certificate-expired/</guid><category>2022-05-27T21:18:00-00:00</category><description>&lt;p&gt;[Open Issue]
The SSL certificate on &lt;a href="https://pkg.jenkins.io"&gt;pkg.jenkins.io&lt;/a&gt; and &lt;a href="https://updates.jenkins-ci.org"&gt;updates.jenkins-ci.org&lt;/a&gt; have expired.
The SSL certificate on &lt;a href="https://updates.jenkins.io"&gt;updates.jenkins.io&lt;/a&gt; has &lt;strong&gt;not expired&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on updates.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-27-maintenance-updates/</link><pubDate>Fri, 27 May 2022 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-27-maintenance-updates/</guid><category>2022-05-27T17:00:00-00:00</category><description>&lt;p&gt;[Initial message]
We are performing a maintenance on the virtual machine hosting the website &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; (&amp;ldquo;Update Center&amp;rdquo;) as part of &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2888"&gt;https://github.com/jenkins-infra/helpdesk/issues/2888&lt;/a&gt;.
No disruption is expected (unless a human mistake is made of course).&lt;/p&gt;</description></item><item><title>[Resolved] Outage on updates.jenkins.io - Invalid certificate</title><link>https://status.jenkins.io/issues/2022-05-19-outage-updates/</link><pubDate>Thu, 19 May 2022 08:10:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-19-outage-updates/</guid><category>2022-05-19T09:10:00-00:00</category><description>&lt;p&gt;[edit]
Fix applied, but it should take up to 1 hour depending on the DNS cache of your internet providers.
More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254"&gt;https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
The website updates.jenkins.io is responding either HTTP/404 pages or &amp;ldquo;Invalid certificate&amp;rdquo; (when accessed through HTTPS).&lt;/p&gt;</description></item><item><title>[Resolved] AKS outage, impacts on infra.ci.jenkins.io and ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-17-infra-ci/</link><pubDate>Tue, 17 May 2022 15:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-17-infra-ci/</guid><category>2022-05-17T17:30:00-00:00</category><description>&lt;p&gt;[close]
AKS outage finished: everything is back to normal.&lt;/p&gt;
&lt;p&gt;[update]
There is an AKS outage on US East 2, which impacts the Virtual Machines allocation: &lt;a href="https://app.azure.com/h/MSR7-9Z0/dffcf0"&gt;https://app.azure.com/h/MSR7-9Z0/dffcf0&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;[infra.ci.jenkins.io] No builds using Kubernetes-based agent can be executed. &amp;ldquo;Website Pull Requests preview&amp;rdquo; feature is unavailable.
&lt;ul&gt;
&lt;li&gt;Cause: The Kubernetes cluster &lt;code&gt;temp-privatek8s&lt;/code&gt; is unable to launch new Virtual machines nodes: infra.ci.jenkins.io cannot handle builds.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;[ci.jenkins.io] Increased build queue as only AWS is used for Docker Agents virtual machines.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[initial message]
Cluster automatic scaling to handle builds is not working anymore on infra.ci.jenkins.io so it may have difficulties with builds and it could also impact the preview system used within &lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-17-maintenance-ci/</link><pubDate>Tue, 17 May 2022 11:31:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-17-maintenance-ci/</guid><category>2022-05-17T12:24:00-00:00</category><description>&lt;p&gt;An upgrade of the plugins of ci.jenkins.io has been started.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://www.jenkins.io/security/advisory/2022-05-17/"&gt;the 2022-05-17 security advisory&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] JFrog's Artifactory unavailable (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-05-13-artifactory-down/</link><pubDate>Fri, 13 May 2022 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-13-artifactory-down/</guid><category>2022-05-13T11:00:00-00:00</category><description>&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We were alerted by some users that the JFrog&amp;rsquo;s Artifactory service at &lt;a href="https://repo.jenkins-ci.org"&gt;https://repo.jenkins-ci.org&lt;/a&gt; is unavailable.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2933"&gt;https://github.com/jenkins-infra/helpdesk/issues/2933&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on pkg.jenkins.io and mirrors.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-07-maintenance-pkg-mirror-jenkins-io/</link><pubDate>Sat, 07 May 2022 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-07-maintenance-pkg-mirror-jenkins-io/</guid><category>2022-05-07T09:13:00-00:00</category><description>&lt;p&gt;[Open Issue]
The VM hosting the services mirror.jenkins.io and pk.jenkins.io is slow to respond.
The person on-call received alerts last night and had to operate.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re going to increase the size of the VM and its disk as a short-term measure: both services will be down while the VM is restarted.&lt;/p&gt;</description></item><item><title>[Resolved] JFrog's Artifactory unavailable (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-05-05-artifactory-down/</link><pubDate>Thu, 05 May 2022 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-05-artifactory-down/</guid><category>2022-05-06T20:12:00-00:00</category><description>&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We were alerted by some users that the JFrog&amp;rsquo;s Artifactory service at &lt;a href="https://repo.jenkins-ci.org"&gt;https://repo.jenkins-ci.org&lt;/a&gt; is unavailable.&lt;/p&gt;
&lt;p&gt;Requests to hte service answers HTTP/5XX errors and the error page at &lt;a href="https://repo.jenkins-ci.org/ui/"&gt;https://repo.jenkins-ci.org/ui/&lt;/a&gt; mentions unhealthy services.&lt;/p&gt;
&lt;p&gt;We are working with JFrog to put this service back.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2920"&gt;https://github.com/jenkins-infra/helpdesk/issues/2920&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Migration of rating.jenkins.io from amazon to azure</title><link>https://status.jenkins.io/issues/2022-05-02-migration-rating/</link><pubDate>Tue, 03 May 2022 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-02-migration-rating/</guid><category>2022-05-03T07:55:00-00:00</category><description>&lt;p&gt;Migration done, nothing to report.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll do a migration of rating.jenkins.io from amazon to azure this Tuesday, 6th of May 2022, starting at 7:30 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/1627"&gt;https://github.com/jenkins-infra/helpdesk/issues/1627&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-02-ci-outage/</link><pubDate>Mon, 02 May 2022 18:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-02-ci-outage/</guid><category>2022-05-02T21:32:00-00:00</category><description>&lt;p&gt;The &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; service saturated its CPU with Java JIT compilation and Pipeline library loading.
Diagnostic information was captured and the service was restarted.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-01-ci-outage/</link><pubDate>Sun, 01 May 2022 12:58:27 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-01-ci-outage/</guid><category>2022-05-01T13:59:33-00:00</category><description>&lt;p&gt;Undiagnosed outage of &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; service.
Service was restored without intervention.&lt;/p&gt;</description></item><item><title>[Resolved] JFrog's Artifactory WebUI unavailable (repo.jenkins-ci.org)</title><link>https://status.jenkins.io/issues/2022-04-28-artifactory-ui/</link><pubDate>Thu, 28 Apr 2022 04:47:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-28-artifactory-ui/</guid><category>2022-04-29T15:09:00-00:00</category><description>&lt;p&gt;[Closing message]
JFrogs resolve the issue by restarting the server dealing with the UI&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;We were alerted by some users that the Web UI of the JFrog&amp;rsquo;s Artifactory service at &lt;a href="https://repo.jenkins-ci.org/ui"&gt;https://repo.jenkins-ci.org/ui&lt;/a&gt; is unavailable: it answers HTTP/503 errors with an error page.&lt;/p&gt;
&lt;p&gt;This outage does NOT affect the ability to download or upload artefacts in the service.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2904"&gt;https://github.com/jenkins-infra/helpdesk/issues/2904&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2022-04-26-maintenance-aks-k8s/</link><pubDate>Wed, 27 Apr 2022 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-26-maintenance-aks-k8s/</guid><category>2022-04-27T12:45:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;ll do an AKS clusters upgrade from 1.20 to 1.21 this Wednesday, 27th of April 2022, starting at 11:00 UTC.&lt;/p&gt;
&lt;p&gt;See more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2866"&gt;https://github.com/jenkins-infra/helpdesk/issues/2866&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Maintenance on issues.jenkins.io (JIRA)</title><link>https://status.jenkins.io/issues/2022-04-21-jira-lts-upgrade/</link><pubDate>Thu, 21 Apr 2022 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-21-jira-lts-upgrade/</guid><category>2022-04-22T00:00:00-00:00</category><description>&lt;p&gt;The Linux Foundation team that maintains our Jira instance will upgrade the JIRA instance at &lt;a href="https://issues.jenkins.io"&gt;https://issues.jenkins.io&lt;/a&gt; to the latest LTS version.&lt;/p&gt;
&lt;p&gt;More information in the following issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2872"&gt;https://github.com/jenkins-infra/helpdesk/issues/2872&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Disruptions on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-04-20-issue-ci/</link><pubDate>Wed, 20 Apr 2022 16:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-20-issue-ci/</guid><category>2022-04-21T14:45:00-00:00</category><description>&lt;p&gt;[Closing Incident]
The service ci.jenkins.io is now performing as expected. A post-mortem is expected in the upcoming days, please follow up on the issue &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2893"&gt;https://github.com/jenkins-infra/helpdesk/issues/2893&lt;/a&gt; if you are interested.&lt;/p&gt;
&lt;p&gt;[Opening Incident]
There are disruptions on the service ci.jenkins.io, see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2893"&gt;https://github.com/jenkins-infra/helpdesk/issues/2893&lt;/a&gt; for more details and progress.&lt;/p&gt;</description></item><item><title>[Resolved] Outage on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-04-12-ci-outage/</link><pubDate>Tue, 12 Apr 2022 11:07:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-12-ci-outage/</guid><category>2022-04-12T12:20:26-00:00</category><description>&lt;p&gt;The &lt;a href="https://ci.jenkins.io"&gt;ci.jenkins.io&lt;/a&gt; service went offline and returned to service as reported by uptime robot.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window for Ingress Controllers of Kubernetes Clusters</title><link>https://status.jenkins.io/issues/2022-04-08-maintenance-window-ingress-kubes/</link><pubDate>Fri, 08 Apr 2022 10:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-08-maintenance-window-ingress-kubes/</guid><category>2022-04-08T11:45:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The maintenance has been completed, all services are operational.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;A maintenance on the ingress controller of the Azure Kubernetes clusters &lt;code&gt;publick8s&lt;/code&gt; and &lt;code&gt;temp-privatek8s&lt;/code&gt; is planned for the 08th of April 2022, around 10:30am UTC.&lt;/p&gt;
&lt;p&gt;No global outage are expected, but there could be minor impacts (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reference: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2875"&gt;https://github.com/jenkins-infra/helpdesk/issues/2875&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Artifactory is slow</title><link>https://status.jenkins.io/issues/2022-04-04-artifactory-slow/</link><pubDate>Mon, 04 Apr 2022 07:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-04-04-artifactory-slow/</guid><category>2022-04-04T13:36:00-00:00</category><description>&lt;p&gt;[Closing message]
The incident was automatically closed in our monitoring system at 13:35 UTC, with the average response time going below the alerting threshold.&lt;/p&gt;
&lt;p&gt;[Initial message]
We were alerted in parallel by some users and our monitoring that JFrog Artifactory service (repo.jenkins-ci.org) is slow to answer to requests, leading to slowness when downloading artifacts, and eventually build failures due to timeout.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2864"&gt;https://github.com/jenkins-infra/helpdesk/issues/2864&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance operation on infra.ci.jenkins.io + jenkins.io's pull requests</title><link>https://status.jenkins.io/issues/2022-03-30-infra.ci-maintenance/</link><pubDate>Wed, 30 Mar 2022 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-03-30-infra.ci-maintenance/</guid><category>2022-03-30T22:30:00-00:00</category><description>&lt;p&gt;[Initial message]
As part of &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2840"&gt;https://github.com/jenkins-infra/helpdesk/issues/2840&lt;/a&gt;, the Jenkins infra team will perform a maintenance to infra.ci.jenkins.io.&lt;/p&gt;
&lt;p&gt;Impact is for the contributors: the previews on the GitHub pull requests for jenkins.io will fail until the operation is completed.&lt;/p&gt;</description></item><item><title>[Resolved] Artifactory is slow</title><link>https://status.jenkins.io/issues/2022-03-23-artifactory-slow/</link><pubDate>Wed, 23 Mar 2022 14:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-03-23-artifactory-slow/</guid><category>2022-03-24T22:38:00-00:00</category><description>&lt;p&gt;[Final message]
Incident was tracked and covered by JFrog: &lt;a href="https://status.jfrog.io/incidents/8hh7t43bs0xt"&gt;https://status.jfrog.io/incidents/8hh7t43bs0xt&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We were alerted in parallel by some users and our monitoring that JFrog Artifactory service (repo.jenkins-ci.org) is slow to answer to requests, leading to slowness when downloading artifacts, and eventually build failures due to timeout.&lt;/p&gt;
&lt;p&gt;We are working on it, see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2849"&gt;https://github.com/jenkins-infra/helpdesk/issues/2849&lt;/a&gt; for more details.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-03-15-maintenance-ci/</link><pubDate>Tue, 15 Mar 2022 13:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-03-15-maintenance-ci/</guid><category>2022-03-15T15:45:00-00:00</category><description>&lt;p&gt;An upgrade of the plugins of ci.jenkins.io has been started. More informations to come.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on AKS</title><link>https://status.jenkins.io/issues/2022-03-08-maintenance-k8s/</link><pubDate>Tue, 08 Mar 2022 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-03-08-maintenance-k8s/</guid><category>2022-03-08T11:00:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;Maintenance finished. LDAP was unavailable during restart from 10:10 UTC until 10:15 UTC as per &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2810"&gt;https://github.com/jenkins-infra/helpdesk/issues/2810&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;A maintenance on the ingress controller of our Azure Kubernetes clusters (&lt;code&gt;publick8s&lt;/code&gt; and &lt;code&gt;temp-privatek8s&lt;/code&gt;) is planned for the 08th of March at 08:00am UTC.&lt;/p&gt;
&lt;p&gt;No global outage are expected, but there could be minor impacts (1-2 min outage) on the following services if there are any unexpected upgrade issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reference: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2809"&gt;jenkins-infra/helpdesk#2809&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Problems publishing artifacts in Artifactory (2022-03-04)</title><link>https://status.jenkins.io/issues/2022-03-04-artifactory-out-of-space/</link><pubDate>Fri, 04 Mar 2022 18:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-03-04-artifactory-out-of-space/</guid><category>2022-03-07T10:45:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;The repository has been cleaned up (~120 Gb) and additional measures are being applied to stay under the storage limit.
Deploy to the repository can be done again.&lt;/p&gt;
&lt;p&gt;[Initial Message]
We&amp;rsquo;ve observed problems publishing artifacts in Artifactory, logs indicate the disk is full. So if you&amp;rsquo;re unable to release stuff the next few days, that is probably why.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://groups.google.com/g/jenkinsci-dev/c/TZakKUjUm9Q/m/Pirq0fqEBAAJ?utm_medium=email&amp;amp;utm_source=footer"&gt;https://groups.google.com/g/jenkinsci-dev/c/TZakKUjUm9Q/m/Pirq0fqEBAAJ?utm_medium=email&amp;amp;utm_source=footer&lt;/a&gt; as followup&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance window on ci.jenkins.io (2022-02-15)</title><link>https://status.jenkins.io/issues/2022-02-15-maintenance-window-ci/</link><pubDate>Tue, 15 Feb 2022 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-02-15-maintenance-window-ci/</guid><category>2022-02-15T14:45:00-00:00</category><description>&lt;p&gt;The 2022-02-15 at 13:30 UTC, expect an outage on ci.jenkins to update the plugins installed on this instance.&lt;/p&gt;
&lt;p&gt;Security advisory is available at &lt;a href="https://www.jenkins.io/security/advisory/2022-02-15/"&gt;https://www.jenkins.io/security/advisory/2022-02-15/&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maven agents not allocating on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-02-10-agents-not-allocating-ci/</link><pubDate>Fri, 11 Feb 2022 02:14:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-02-10-agents-not-allocating-ci/</guid><category>2022-02-14T19:00:00-00:00</category><description>&lt;p&gt;[Update 11th of February 2022 - 19:00 UTC]
An operation is required on the underlying Kubernetes cluster. We plan to do it monday 14th starting at 08:00am UTC.&lt;/p&gt;
&lt;p&gt;It will result in a downtime of all the agents with labels &lt;code&gt;maven&lt;/code&gt; and &lt;code&gt;maven-11&lt;/code&gt;: builds will be queued until the cluster is working again.
VM agents will keep being allocated.&lt;/p&gt;
&lt;p&gt;[Update 11th of February 2022 - 15:20 UTC]
Cluster had been scaled manually to handle builds until the root cause is fixed.
Read more at &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2780"&gt;https://github.com/jenkins-infra/helpdesk/issues/2780&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Agents with labels &lt;code&gt;maven&lt;/code&gt; and &lt;code&gt;maven-11&lt;/code&gt; fail to allocate on AWS.
Infrastructure team found that the AWS autoscaler was failing.
Investigation is in progress.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-02-09-maintenance-window-ci/</link><pubDate>Wed, 09 Feb 2022 12:14:28 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-02-09-maintenance-window-ci/</guid><category>2022-02-09T12:55:38-00:00</category><description>&lt;p&gt;An upgrade of ci.jenkins.io from 2.319.2 to 2.319.3.
See &lt;a href="https://www.jenkins.io/security/advisory/2022-02-09/"&gt;security advisory&lt;/a&gt;, &lt;a href="https://www.jenkins.io/changelog-stable/#v2.319.3"&gt;changelog&lt;/a&gt;, and &lt;a href="https://www.jenkins.io/doc/upgrade-guide/2.319/#upgrading-to-jenkins-lts-2-319-3"&gt;upgrade guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] TLS error `SSL_ERROR_BAD_CERT_DOMAIN` on mirrors.jenkins.io and mirrors.jenkins-ci</title><link>https://status.jenkins.io/issues/2022-02-07-tls-mirrors/</link><pubDate>Mon, 07 Feb 2022 12:37:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-02-07-tls-mirrors/</guid><category>2022-02-07T12:57:00-00:00</category><description>&lt;p&gt;[Final message]
The datadog alert on the https call &lt;a href="https://github.com/jenkins-infra/datadog/pull/56"&gt;has been removed&lt;/a&gt; as this service as never been served as https.&lt;/p&gt;
&lt;p&gt;[Initial message]
The services mirrors.jenkins-ci.org and mirrors.jenkins.io shows an error &lt;code&gt;SSL_ERROR_BAD_CERT_DOMAIN&lt;/code&gt; due to a certificate generated with the wrong name.
Only HTTPS (with TLS) access is impacted: plain HTTP is still working as expected.&lt;/p&gt;
&lt;p&gt;We are investigating the problem.&lt;/p&gt;</description></item><item><title>[Resolved] ci.jenkins.io down due to overload</title><link>https://status.jenkins.io/issues/2022-01-21-overload-outage-ci/</link><pubDate>Fri, 21 Jan 2022 17:56:43 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-01-21-overload-outage-ci/</guid><category>2022-01-21T18:15:40-00:00</category><description>&lt;p&gt;Overload detected on ci.jenkins.io required a service restart.
Reported to Mark Waite email by uptimerobot.&lt;/p&gt;</description></item><item><title>[Resolved] repo.jenkins-ci.org down</title><link>https://status.jenkins.io/issues/2022-01-17-repo-jenkins-ci-org/</link><pubDate>Mon, 17 Jan 2022 10:38:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-01-17-repo-jenkins-ci-org/</guid><category>2022-01-17T11:27:00-00:00</category><description>&lt;p&gt;[Final message]
The service is back to normal.&lt;/p&gt;
&lt;p&gt;[Initial message]
The service repo.jenkins-ci.org is down.
A ticket has been raised with JFrog support.&lt;/p&gt;</description></item><item><title>[Resolved] Disruptions on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-01-13-issue-ci/</link><pubDate>Thu, 13 Jan 2022 15:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-01-13-issue-ci/</guid><category>2022-01-21T12:30:00-00:00</category><description>&lt;p&gt;There are disruptions on the service ci.jenkins.io, see &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/2733"&gt;https://github.com/jenkins-infra/helpdesk/issues/2733&lt;/a&gt; for more details and progress.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2022-01-12-maintenance-window-ci/</link><pubDate>Wed, 12 Jan 2022 14:44:54 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-01-12-maintenance-window-ci/</guid><category>2022-01-12T16:49:55-00:00</category><description>&lt;p&gt;An upgrade of ci.jenkins.io from 2.319.1 to 2.319.2.
See &lt;a href="https://www.jenkins.io/security/advisory/2022-01-12/"&gt;security advisory&lt;/a&gt;, &lt;a href="https://www.jenkins.io/changelog-stable/#v2.319.2"&gt;changelog&lt;/a&gt;, and &lt;a href="https://www.jenkins.io/doc/upgrade-guide/2.319/#upgrading-to-jenkins-lts-2-319-2"&gt;upgrade guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on AKS</title><link>https://status.jenkins.io/issues/2021-12-20-maintenance-window-aks/</link><pubDate>Mon, 20 Dec 2021 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-12-20-maintenance-window-aks/</guid><category>2021-12-20T11:30:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The maintenance has been completed, all services are operational.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;A maintenance on the ingress controller of the Azure Kubernetes cluster &lt;code&gt;publick8s&lt;/code&gt; is planned for the 20th of December, around 11:00am UTC.&lt;/p&gt;
&lt;p&gt;No global outage are expected, but there could be minor impacts (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reference: &lt;a href="https://github.com/jenkins-infra/kubernetes-management/pull/1748"&gt;https://github.com/jenkins-infra/kubernetes-management/pull/1748&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Jira (issues.jenkins.io) outage</title><link>https://status.jenkins.io/issues/2021-12-15-jira-outage/</link><pubDate>Wed, 15 Dec 2021 15:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-12-15-jira-outage/</guid><category>2021-12-15 16:05:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;The outage was due to an external problem with AWS.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;The JIRA instance at issues.jenkins.io, managed by the Linux Foundation team, is currently down.&lt;/p&gt;
&lt;p&gt;We are escalating and trying to fix the issue.&lt;/p&gt;</description></item><item><title>[Resolved] accounts.jenkins.io down</title><link>https://status.jenkins.io/issues/2021-12-10-accounts-down/</link><pubDate>Fri, 10 Dec 2021 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-12-10-accounts-down/</guid><category>2021-12-15T15:00:00-00:00</category><description>&lt;p&gt;[Final Message]&lt;/p&gt;
&lt;p&gt;Our investigations showed we are not vulnerable to the CVE-2021-44228 nor the CVE-2021-45046.&lt;/p&gt;
&lt;p&gt;[Initial Message]&lt;/p&gt;
&lt;p&gt;We decided to disable the Jenkins accounts service temporarily out of an abundance of caution.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://www.jenkins.io/blog/2021/12/10/log4j2-rce-CVE-2021-44228/"&gt;the Jenkins blog post about CVE-2021-44228&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2021-11-25-maintenance-k8s/</link><pubDate>Thu, 25 Nov 2021 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-11-25-maintenance-k8s/</guid><category>2021-11-25T12:00:00-00:00</category><description>&lt;p&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-3118"&gt;INFRA-3118&lt;/a&gt;
&lt;a href="https://github.com/jenkins-infra/documentation/blob/main/maintenance/kubernetes/aks-1.20.md"&gt;Notes&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Final Message]
The upgrade is finished without any incident, all services are up and running.&lt;/p&gt;
&lt;p&gt;Cat tax:
&lt;img src="https://d33wubrfki0l68.cloudfront.net/688a7bc98d1e09112a54286a9282073c7bf5ee78/5cff4/images/blog/2020-12-08-kubernetes-1.20-release-announcement/laser.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;[Initial Message]
We&amp;rsquo;ll do an AKS and EKS clusters upgrade from 1.19 to 1.20 this Thursday, 25th of November 2021, starting at 08:00 UTC.&lt;/p&gt;
&lt;p&gt;The service &lt;code&gt;ldap.jenkins.io&lt;/code&gt; service might have a downtime due to its PV.&lt;/p&gt;
&lt;p&gt;Other services might have a downtime too if their probes take more than one second to respond due to the new &lt;code&gt;timeoutPeriod&lt;/code&gt; enforced default value.&lt;br&gt;
Note: the official Jenkins helm chart we&amp;rsquo;re using has already &lt;a href="https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/values.yaml#L150-L168"&gt;set the default timeout period to 5 seconds&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Apart from that, no outage is expected, but there could be an impact (1-2 min outage) on the following services if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] jenkins.io outage</title><link>https://status.jenkins.io/issues/2021-11-18-jenkins-io-outage/</link><pubDate>Thu, 18 Nov 2021 10:47:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-11-18-jenkins-io-outage/</guid><category>2021-11-05T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The website jenkins.io and all its sub pages are back online.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The website jenkins.io and all its sub pages (blog, documentation) are experimenting an outage: TLS errors and HTTP/503.
We are working on this outage.&lt;/p&gt;</description></item><item><title>[Resolved] HTTP access to archives.jenkins.io unreachable</title><link>https://status.jenkins.io/issues/2021-11-05-archives-jenkins-io-maintenance/</link><pubDate>Fri, 05 Nov 2021 16:49:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-11-05-archives-jenkins-io-maintenance/</guid><category>2021-11-05T16:50:00-00:00</category><description>&lt;p&gt;The system needed an operating system restart to use the most recent kernel patch.
The operating system patch install and restart was completed with 60 seconds or less of downtime.&lt;/p&gt;
&lt;p&gt;The SSL certificate on archives.jenkins.io was scheduled to expire in less than 10 days.
The issue was resolved by using the notes from a ci.jenkins.io certificate renewal failure that is recorded in the Jenkins infra runbook.
No outage due to the SSL certificate renewal, just prevented an outage when the certificate would expire.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-11-04-maintenance-window-ci/</link><pubDate>Thu, 04 Nov 2021 11:24:40 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-11-04-maintenance-window-ci/</guid><category>2021-11-04T12:07:34-00:00</category><description>&lt;p&gt;An upgrade of ci.jenkins.io from 2.303.2 to 2.303.3.
See &lt;a href="https://www.jenkins.io/security/advisory/2021-11-04/"&gt;security advisory&lt;/a&gt;, &lt;a href="https://www.jenkins.io/changelog-stable/#v2.303.3"&gt;changelog&lt;/a&gt;, and &lt;a href="https://www.jenkins.io/doc/upgrade-guide/2.303/#upgrading-to-jenkins-lts-2-303-3"&gt;upgrade guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance on Plugin Site</title><link>https://status.jenkins.io/issues/2021-10-26-maintenance-plugin-site/</link><pubDate>Tue, 26 Oct 2021 15:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-10-26-maintenance-plugin-site/</guid><category>2021-10-26T17:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The service is back online.&lt;/p&gt;
&lt;p&gt;[Initial Message]
A maintenance on the Plugin site is planned, to upgrade its dependencies and fix an ongoing DNS issue.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The website plugins.jenkins.io should not be impacted as it&amp;rsquo;s cached by a CDN, worst case scenario is an outage of ~1 min time to rollback&lt;/li&gt;
&lt;li&gt;The website plugins.origin.jenkins.io will be stopped for the duration of the maintenance&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Maintenance Window on AKS</title><link>https://status.jenkins.io/issues/2021-10-25-maintenance-window-aks/</link><pubDate>Tue, 26 Oct 2021 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-10-25-maintenance-window-aks/</guid><category>2021-10-26T14:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The maintenance has been completed, all services are operational.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[Edit - Monday 25th]&lt;/p&gt;
&lt;p&gt;We had to delay the operation as we discovered last minutes items to be changed.
Next operation window is planned Tuesday, the 26th of October, at 08:30am UTC.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;[Initial Message - Friday 22th]&lt;/p&gt;
&lt;p&gt;A maintenance on the ingress controller of the Azure Kubernetes cluster &lt;code&gt;publick8s&lt;/code&gt; is planned for the 25th of October, around 12:00am (noon) UTC.&lt;/p&gt;
&lt;p&gt;No outage is expected, but there could be an impact (1-2 min outage) on the following service if there is an unexpected upgrade issue:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reference: &lt;a href="https://github.com/jenkins-infra/charts/pull/1424"&gt;https://github.com/jenkins-infra/charts/pull/1424&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-10-06-maintenance-window-ci/</link><pubDate>Wed, 06 Oct 2021 15:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-10-06-maintenance-window-ci/</guid><category>2021-10-06T16:09:00-00:00</category><description>&lt;p&gt;Jenkins core and plugins were updated on ci.jenkins.io with security fixes from &lt;a href="https://www.jenkins.io/security/advisory/2021-10-06/"&gt;Jenkins security advisory 2021-10-06&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Convert Jira database to utf8mb4</title><link>https://status.jenkins.io/issues/2021-10-05-maintenance-jira-rds/</link><pubDate>Tue, 05 Oct 2021 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-10-05-maintenance-jira-rds/</guid><category>2021-10-05 18:00:00</category><description>&lt;p&gt;The Linux Foundation will convert Jira database and tables from utf8 to utf8mb4 and solve collation errors in Jira.
issues.jenkins.io will be unavailable during the maintenance&lt;/p&gt;
&lt;p&gt;&lt;a href="https://twitter.com/jenkinsci/status/..."&gt;Twitter&lt;/a&gt;
&lt;a href="https://groups.google.com/u/1/g/jenkins-infra/c/..."&gt;Discussion&lt;/a&gt;
&lt;a href="https://issues.jenkins.io/"&gt;Jira&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] LDAP server down</title><link>https://status.jenkins.io/issues/2021-10-01-ldap-outage/</link><pubDate>Fri, 01 Oct 2021 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-10-01-ldap-outage/</guid><category>2021-10-04 09:55:00</category><description>&lt;p&gt;[Final Message]
The root certificate have been rotated, resulting in an automatic repair of all broken services.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;archives.jenkins.io was back online at 09:55 UTC&lt;/li&gt;
&lt;li&gt;ci.jenkins.io was back online at 09:55 UTC&lt;/li&gt;
&lt;li&gt;ldap was back online at 09:55 UTC&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
Due to &lt;a href="https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/"&gt;DST Root CA X3 Expiration&lt;/a&gt; our LDAP server is currently down, we are working to fix it.&lt;/p&gt;</description></item><item><title>[Resolved] Puppet Outage on VM-hosted services</title><link>https://status.jenkins.io/issues/2021-09-23-puppet-outage/</link><pubDate>Thu, 23 Sep 2021 10:01:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-09-23-puppet-outage/</guid><category>2021-09-20T13:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The Puppet infrastructure had been fixed, resulting in an automatic repair of all broken services.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;archives.jenkins.io was back online at 12:58 UTC&lt;/li&gt;
&lt;li&gt;ci.jenkins.io was back online at 13:00 UTC&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
An outage on our Puppet infrastructure system is currently happening.&lt;/p&gt;
&lt;p&gt;A mitigation had been applied resulting in disabling configuration update to avoid breaking services.&lt;/p&gt;
&lt;p&gt;The following services had been put down before we could mitigate:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ci.jenkins.io&lt;/li&gt;
&lt;li&gt;archives.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We are working on fixing these services and the Puppet infrastructure&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance with downtime on the AKS (Azure Kubernetes Service) cluster `publick8s`</title><link>https://status.jenkins.io/issues/2021-09-20-aks-maintenance/</link><pubDate>Mon, 20 Sep 2021 09:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-09-20-aks-maintenance/</guid><category>2021-09-20T10:10:00-00:00</category><description>&lt;p&gt;[Final Message]
The AKS cluster was upgraded successfully to ensure that &lt;a href="https://github.com/Azure/AKS/issues/2547"&gt;CVE-2021-25741&lt;/a&gt; is fixed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;AKS Control plane is now using Kubernetes 1.19.13&lt;/li&gt;
&lt;li&gt;AKS Node pools are all using &lt;a href="https://github.com/Azure/AKS/releases/tag/2021-09-09"&gt;https://github.com/Azure/AKS/releases/tag/2021-09-09&lt;/a&gt; images&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
A maintenance on the AKS cluster that requires a restart of each service and node is currently applied.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The services &lt;code&gt;ldap.jenkins.io&lt;/code&gt; and &lt;code&gt;plugins.jenkins.io&lt;/code&gt; will be restarted
with an expected downtime of 3 to 5 minutes (time for AKS to bind the data volumes)&lt;/li&gt;
&lt;li&gt;All other services should remain up and running.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Jenkins wiki offline due to vulnerability</title><link>https://status.jenkins.io/issues/2021-09-02-wiki-offline/</link><pubDate>Thu, 02 Sep 2021 08:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-09-02-wiki-offline/</guid><category>2021-11-03T15:30:00-00:00</category><description>&lt;p&gt;[Final Message]
The service is back online in the form of an nginx image serving the exported confluence data as HTML.&lt;/p&gt;
&lt;p&gt;Ref: &lt;a href="https://issues.jenkins.io/projects/INFRA/issues/INFRA-3092"&gt;Service to redirect wiki requests to exported Confluence content or to a search on jenkins.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Initial Message]
Jenkins wiki, &lt;a href="https://wiki.jenkins.io"&gt;https://wiki.jenkins.io&lt;/a&gt;, is offline due to a remote code execution security vulnerability.&lt;/p&gt;</description></item><item><title>[Resolved] Restart Jenkins wiki https://wiki.jenkins.io</title><link>https://status.jenkins.io/issues/2021-08-31-wiki-maintenance/</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-08-31-wiki-maintenance/</guid><category>2021-09-01T00:15:00-00:00</category><description>&lt;p&gt;Jenkins wiki needs to be restarted about once a month.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-08-31-maintenance-window-ci/</link><pubDate>Tue, 31 Aug 2021 12:36:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-08-31-maintenance-window-ci/</guid><category>2021-08-31T14:14:08-00:00</category><description>&lt;p&gt;Plugins were updated on ci.jenkins.io with security fixes from &lt;a href="https://www.jenkins.io/security/advisory/2021-08-31/"&gt;Jenkins security advisory 2021-08-31&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance with downtime on https://wiki.jenkins.io (Jenkins wiki)</title><link>https://status.jenkins.io/issues/2021-08-29-wiki-maintenance/</link><pubDate>Sun, 29 Aug 2021 18:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-08-29-wiki-maintenance/</guid><category>2021-08-29T18:03:00-00:00</category><description>&lt;p&gt;SSL certificate on the Jenkins wiki will expire in 14 days.
Restart the Apache service to use the new certificate.&lt;/p&gt;
&lt;p&gt;Downtime less than 3 minutes.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance with downtime on https://repo.jenkins-ci.org (JFrog repository service)</title><link>https://status.jenkins.io/issues/2021-08-26-jfrog-maintenance/</link><pubDate>Fri, 27 Aug 2021 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-08-26-jfrog-maintenance/</guid><category>2021-08-27T13:05:00-00:00</category><description>&lt;p&gt;[Update] Intervention done successfully with 5 minutes downtime only.&lt;/p&gt;
&lt;p&gt;JFrog support team will perform a maintenance on their service that will impact our repository at &lt;a href="https://repo.jenkins-ci.org"&gt;https://repo.jenkins-ci.org&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A downtime of almost 30 minutes is expected, starting at 13:00 UTC (01:00pm UTC), the 27th of August 2021.&lt;/p&gt;</description></item><item><title>[Resolved] HTTP access to archives.jenkins.io unreachable</title><link>https://status.jenkins.io/issues/2021-07-16-archives-jenkins-io-unreachable/</link><pubDate>Fri, 16 Jul 2021 23:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-07-16-archives-jenkins-io-unreachable/</guid><category>2021-07-17T15:10:00-00:00</category><description>&lt;p&gt;The HTTP server on archives.jenkins.io was not responding to requests.
The mirror system on get.jenkins.io excluded archives.jenkins.io because it was unreachable.
Issue was resolved by stopping and starting the apache2 service on the host (okra.jenkins.io).&lt;/p&gt;</description></item><item><title>[Resolved] Update center content not refreshed, recent plugin releases not visible</title><link>https://status.jenkins.io/issues/2021-07-07-update-center-not-refreshed/</link><pubDate>Wed, 07 Jul 2021 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-07-07-update-center-not-refreshed/</guid><category>2021-07-12T07:02:00-00:00</category><description>&lt;p&gt;The update center had its content not refreshed from the 07th of July 2021
until the 12th of July 2021.&lt;/p&gt;
&lt;p&gt;More details on what went wrong and how it was fixed can be found in the following page:
&lt;a href="https://issues.jenkins.io/browse/INFRA-3023"&gt;INFRA-3023&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-06-21-maintenance-window-ci/</link><pubDate>Mon, 21 Jun 2021 10:04:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-21-maintenance-window-ci/</guid><category>2021-06-21T10:06:00-00:00</category><description>&lt;p&gt;Update: operation took 2 minutes, and restart was successful&lt;/p&gt;
&lt;p&gt;==============================&lt;/p&gt;
&lt;p&gt;A restart of ci.jenkins.io is planned with the following changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-3010"&gt;https://issues.jenkins.io/browse/INFRA-3010&lt;/a&gt; =&amp;gt; Remove the plugin azure-commons&lt;/li&gt;
&lt;li&gt;Plugins upgrade:
&lt;ul&gt;
&lt;li&gt;Bump ec2-plugin to &lt;a href="https://github.com/jenkinsci/ec2-plugin/releases/tag/ec2-1.62"&gt;1.62&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump Azure VM to &lt;a href="https://github.com/jenkinsci/azure-vm-agents-plugin/releases/tag/783.v58077630847d"&gt;783.v58077630847d&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump Code Coverage API to &lt;a href="https://github.com/jenkinsci/code-coverage-api-plugin/releases/tag/code-coverage-api-1.4.0"&gt;1.4.0&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump JaCoCo to &lt;a href="https://github.com/jenkinsci/jacoco-plugin/releases/tag/jacoco-3.3.0"&gt;3.3.0&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump Pipeline: Multibranch to &lt;a href="https://github.com/jenkinsci/workflow-multibranch-plugin/releases/tag/workflow-multibranch-2.26"&gt;2.26&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump Pipeline: SCP Step to &lt;a href="https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/CHANGELOG.md#213"&gt;2.13&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Bump Pipeline: Shared Groovy Libraries to &lt;a href="https://github.com/jenkinsci/workflow-cps-global-lib-plugin/releases/tag/workflow-cps-global-lib-2.20"&gt;2.20&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2021-06-17-maintenance-publick8s/</link><pubDate>Thu, 17 Jun 2021 08:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-17-maintenance-publick8s/</guid><category>2021-06-17T09:45:00-00:00</category><description>&lt;p&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-3005"&gt;INFRA-3005&lt;/a&gt;
&lt;a href="https://hackmd.io/EDpvZx9ZS2GWgHHqWFRDfQ?view#118x-to-119x"&gt;NOTES&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[Closing Maintenance]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The update to Kubernetes 1.19.11 was successfully finished at 14:00 UTC&lt;/li&gt;
&lt;li&gt;The service &lt;code&gt;ldap.jenkins.io&lt;/code&gt; had 2 downtimes &lt;a href="https://hackmd.io/8H_OxGydSRiiVGE9VpFcVw#"&gt;post-mortem&lt;/a&gt;,
resulting in authentication not possible on the &lt;a href="https://jira.jenkins.io"&gt;JIRA&lt;/a&gt; and the plugin releases where not possible during the following time windows:
&lt;ul&gt;
&lt;li&gt;From 08:08 UTC until 08:13 UTC (6 min)&lt;/li&gt;
&lt;li&gt;From 10:40 UTC until 10:41 UTC (1 min)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
We&amp;rsquo;ll do an AKS cluster upgrade.&lt;/p&gt;
&lt;p&gt;The service &lt;code&gt;ldap.jenkins.io&lt;/code&gt; service will be restarted.
All other services should remain up and running.&lt;/p&gt;</description></item><item><title>[Resolved] Websites are down</title><link>https://status.jenkins.io/issues/2021-06-08-fastly-outage/</link><pubDate>Tue, 08 Jun 2021 09:58:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-08-fastly-outage/</guid><category>2021-06-08T12:41:00-00:00</category><description>&lt;p&gt;Due to a Fastly world-wide &lt;a href="https://status.fastly.com/incidents/vpk0ssybt3bj"&gt;incident&lt;/a&gt;, three Jenkins services that rely on Fastly to delivery content are impacted.
This outage affects &lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;, &lt;a href="https://pkg.jenkins.io"&gt;pkg.jenkins.io&lt;/a&gt; and &lt;a href="https://plugins.jenkins.io"&gt;plugins.jenkins.io&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Agents randomly disconnected on ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-06-08-ci-agents-disconnect/</link><pubDate>Tue, 08 Jun 2021 05:35:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-08-ci-agents-disconnect/</guid><category>2021-06-08T11:08:00-00:00</category><description>&lt;p&gt;&lt;strong&gt;Update at 2021-06-08 11:20 UTC&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;ci.jenkins.io is back to normal since 2021-06-08 11:08 UTC after running a series of operations including a service full restart.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Initial Message at 2021-06-08 09:35 UTC&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Agents are randomly disconnected on ci.jenkins.io with the following message in pipeline logs:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Channel &amp;#34;hudson.remoting.Channel@&amp;lt;ID&amp;gt;:JNLP4-connect connection from &amp;lt;IP&amp;gt;:&amp;lt;IP:PORT&amp;gt;&amp;#34;: Remote call on JNLP4-connect connection from &amp;lt;IP&amp;gt;:&amp;lt;IP:PORT&amp;gt; failed. The channel is closing down or has closed down
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Builds using an EC2 or a permanent agents are reconnected most of the time but might fail&lt;/li&gt;
&lt;li&gt;Builds on fungible agents such as ACI are failing 100% when this error happens in build logs and need to be replayed&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that ci.jenkins.io might be restarted multiple time until the incident is disconnected.&lt;/p&gt;</description></item><item><title>[Resolved] repo.jenkins-ci.org issues</title><link>https://status.jenkins.io/issues/2021-06-07-repo-jenkins-ci-org/</link><pubDate>Mon, 07 Jun 2021 12:37:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-07-repo-jenkins-ci-org/</guid><category>2021-06-07 16:37:00</category><description>&lt;p&gt;&lt;strong&gt;2021-06-08 07:37:00&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This &lt;a href="https://github.com/jenkins-infra/charts/pull/1238"&gt;PR&lt;/a&gt; persist in time the hotfix we applied.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2021-06-07 16:37:00&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Two IPs have been manually added to ldap.jenkins.io configuration.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2021-06-07 12:37:00&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Due to a recent upgrade done by Jfrog on repo.jenkins-ci.org, authentication is broken.
Everything else seems to be working correctly.&lt;/p&gt;
&lt;p&gt;We are contacting their support.&lt;/p&gt;
&lt;p&gt;Follow up will be communicated on the jenkins-infra mailing.
-&amp;gt; &lt;a href="https://groups.google.com/g/jenkins-infra/c/RIIBjKhL3WY"&gt;here&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] ACI agents fail to allocate for ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-06-03-no-aci-agents-for-ci-jenkins-io/</link><pubDate>Thu, 03 Jun 2021 15:41:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-03-no-aci-agents-for-ci-jenkins-io/</guid><category>2021-06-04T09:02:00-00:00</category><description>&lt;p&gt;ci.jenkins.io is unable to start any ACI agent and there is an increasing build queue.&lt;/p&gt;
&lt;p&gt;Investigation is in progress to resolve the issue and identify the root cause, ci.jenkins.io is put in shutdown mode to limit the amount of builds to be treated.&lt;/p&gt;
&lt;p&gt;[edit]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Plugin and configuration upgrades around EC2 and Azure-* have been done&lt;/li&gt;
&lt;li&gt;all the builds have been cleaned&lt;/li&gt;
&lt;li&gt;ci.jenkins.io restarted and back to normal state&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] Windows LTS Package Unavailable</title><link>https://status.jenkins.io/issues/2021-06-02-lts-windows/</link><pubDate>Wed, 02 Jun 2021 18:59:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-02-lts-windows/</guid><category>2021-06-03T07:03:00-00:00</category><description>&lt;p&gt;Due to a technical issue in the release process, the Windows package for the LTS Jenkins release was unavailable during almost 13 hours.&lt;/p&gt;
&lt;p&gt;The release process has been fixed and executed successfully the 03rd of June 2021 at 06:50 UTC and finished at 07:02 UTC.&lt;/p&gt;
&lt;p&gt;At 07:00 UTC, the Windows package was available again from &lt;a href="https://jenkins.io/download"&gt;https://jenkins.io/download&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] AKS (Azure Kubernetes Service) cluster `publick8s` principal security credential expired</title><link>https://status.jenkins.io/issues/2021-06-03-aks-sp-expiration/</link><pubDate>Wed, 02 Jun 2021 17:53:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-03-aks-sp-expiration/</guid><category>2021-06-03T18:35:00-00:00</category><description>&lt;p&gt;The security credential for the AKS cluster expired the 2021-06-02.&lt;/p&gt;
&lt;p&gt;Any internal request to the Azure API (volume mounts, network integration, etc.) is refused since 2021-06-02T17:53:00-00:00.&lt;/p&gt;
&lt;p&gt;The operation to renew this certificate started at 2021-06-03 - 15:15 UTC and is resulting in all services hosted on the cluster to be restarted.&lt;/p&gt;
&lt;p&gt;No public interuption except for the LDAP service should happen.&lt;/p&gt;
&lt;p&gt;[Edit]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There have been a disruption of nearly 5 min on the service plugins.jenkins.io around 16:00 UTC, reported in the Gitter channel #jenkinsci/docs by Zbynek (thanks!)
Services logs indicate an issue with the Azure file storage while&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] wiki.jenkins.io restart</title><link>https://status.jenkins.io/issues/2021-06-01-maintenance-wiki/</link><pubDate>Tue, 01 Jun 2021 23:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-01-maintenance-wiki/</guid><category>2021-06-01T23:15:00</category><description>&lt;p&gt;The wiki.jenkins.io process will be stopped and restarted.&lt;/p&gt;</description></item><item><title>[Resolved] Update center job on trusted.ci.jenkins.io is blocked</title><link>https://status.jenkins.io/issues/2021-06-01-updates-job-blocked/</link><pubDate>Sun, 30 May 2021 08:13:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-06-01-updates-job-blocked/</guid><category>2021-06-02T01:00:00-00:00</category><description>&lt;p&gt;The Jenkins update center relies on a job that runs periodically on trusted.ci.jenkins.io to record the latest releases.
That job blocked on May 30 and has not been performing updates.&lt;/p&gt;
&lt;h2 id="timeline"&gt;Timeline&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;2021-05-30T08:13 - Update center job on trusted.ci.jenkins.io reports blocked waiting for &lt;code&gt;agent-1&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;2021-06-01T19:45 - Mark Waite investigates Jenkins 2.296 not being visible on &lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;, detects blocked update center job&lt;/li&gt;
&lt;li&gt;2021-06-01T23:50 - EU team hands over, detects there was a DNS resolution issue in trusted.ci.jenkins.io and changed the configuration of &lt;code&gt;agent-1&lt;/code&gt; accordingly: the &lt;code&gt;update_center&lt;/code&gt; build moved from the &amp;ldquo;waiting&amp;rdquo; state to &amp;ldquo;building&amp;rdquo; state on &lt;code&gt;agent-1&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;2021-06-02T01:50 - After a manualy apply of the update_center + a successful build, the latest weekly 2.296 appears on the update center.json&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>[Resolved] ACI agents fail to allocate for ci.jenkins.io</title><link>https://status.jenkins.io/issues/2021-05-29-no-aci-agents-for-ci-jenkins-io/</link><pubDate>Sat, 29 May 2021 22:41:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-05-29-no-aci-agents-for-ci-jenkins-io/</guid><category>2021-05-30T02:11:06-00:00</category><description>&lt;p&gt;A plugin upgrade has caused allocation of Azure Container Instances to fail on ci.jenkins.io. Investigation is in progress to resolve the issue and identify the root cause.&lt;/p&gt;
&lt;p&gt;Issue was resolved by downgrading 5 Azure plugins to the versions that were previously working on ci.jenkins.io&lt;/p&gt;
&lt;h1 id="azure-container-instance-outage-on-cijenkinsio"&gt;Azure Container Instance outage on ci.jenkins.io&lt;/h1&gt;
&lt;h2 id="timeline---may-29-2021"&gt;Timeline - May 29, 2021&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;16:37 Denver - Mark Waite updated plugins on ci.jenkins.io, restarted ci.jenkins.io&lt;/li&gt;
&lt;li&gt;16:55 Denver - Updated JDK 8 tool definition from 8u242 to 8u292&lt;/li&gt;
&lt;li&gt;17:15 Denver - Confirmed builds with JDK 8u292 tools working on amd64, arm64, s390x, and popc64le&lt;/li&gt;
&lt;li&gt;17:39 Denver - Started Jenkins core build, detected that maven and maven-11 agents were not being allocated&lt;/li&gt;
&lt;li&gt;17:41 Denver - System log for ACI agents reports &lt;code&gt;Cannot provision: template for label maven is not available now, because it failed to provision last time.&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;17:50 Denver - Downgraded Azure container plugin to previously installed version, restarted Jenkins&lt;/li&gt;
&lt;li&gt;18:00 Denver - Downgraded plugin reports &lt;code&gt;NoSuchMethodError&lt;/code&gt;, likely indicator that it requires an API in one of the 50+ plugins that were upgraded at 16:37 Denver time&lt;/li&gt;
&lt;li&gt;18:01 Denver - Updated Azure container plugin to latest release&lt;/li&gt;
&lt;li&gt;18:17 Denver - Confirmed problem is still visible after upgrade&lt;/li&gt;
&lt;li&gt;18:19 Denver - Record plugin file system times in case rollback needed&lt;/li&gt;
&lt;li&gt;19:14 Denver - Identify candidate plugins for rollback
&lt;ul&gt;
&lt;li&gt;azure-sdk from 12.vc102aedd3c66 down to 4.vcb202d9010c1&lt;/li&gt;
&lt;li&gt;azure-credentials from 182.v3ccd4a755864 down to 177.v816b81058012&lt;/li&gt;
&lt;li&gt;azure-vm-agents from 780.v50d067d02f76 down to 774.v0cee503baa25&lt;/li&gt;
&lt;li&gt;windows-azure-storage from 358.v5c001416d74f down to 355.v4da08e72a251&lt;/li&gt;
&lt;li&gt;azure-container-agents from 207.v3ad9931bf69e down to 201.v2afdce22b4cf&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Review dependencies of those plugins
&lt;ul&gt;
&lt;li&gt;Used plugin installation manager to install a local copy of those 5 plugins at their previous versions as confirmation that they should be workable at their previous versions as a group. Not a perfect check, but worth the check.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;20:01 Denver - Downgrade those 5 plugins and restart ci.jenkins.io&lt;/li&gt;
&lt;li&gt;20:03 Denver - Restart is complete, Manage Plugins shows those 5 plugins have upgrades available&lt;/li&gt;
&lt;li&gt;20:09 DEnver - Outage resolved, ACI agents are allocated on ci.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="plugins-that-were-upgraded-at-1637-denver-time"&gt;Plugins that were upgraded at 16:37 Denver time&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;-rw-r--r-- 1 jenkins jenkins 4200464 May 29 22:37 plugins/jacoco.jpi
-rw-r--r-- 1 jenkins jenkins 380040 May 29 22:37 plugins/kubernetes.jpi
-rw-r--r-- 1 jenkins jenkins 3091463 May 29 22:37 plugins/ldap.jpi
-rw-r--r-- 1 jenkins jenkins 86675 May 29 22:37 plugins/blueocean-commons.jpi
-rw-r--r-- 1 jenkins jenkins 277630 May 29 22:37 plugins/blueocean-jwt.jpi
-rw-r--r-- 1 jenkins jenkins 39703 May 29 22:37 plugins/command-launcher.jpi
-rw-r--r-- 1 jenkins jenkins 468323 May 29 22:37 plugins/cloudbees-bitbucket-branch-source.jpi
-rw-r--r-- 1 jenkins jenkins 8089625 May 29 22:37 plugins/subversion.jpi
-rw-r--r-- 1 jenkins jenkins 102390 May 29 22:37 plugins/blueocean-rest.jpi
-rw-r--r-- 1 jenkins jenkins 14124 May 29 22:37 plugins/blueocean-jira.jpi
-rw-r--r-- 1 jenkins jenkins 86109 May 29 22:37 plugins/workflow-multibranch.jpi
-rw-r--r-- 1 jenkins jenkins 308017 May 29 22:37 plugins/branch-api.jpi
-rw-r--r-- 1 jenkins jenkins 35870 May 29 22:37 plugins/blueocean-pipeline-scm-api.jpi
-rw-r--r-- 1 jenkins jenkins 2363613 May 29 22:37 plugins/jenkins-design-language.jpi
-rw-r--r-- 1 jenkins jenkins 1076110 May 29 22:37 plugins/blueocean-core-js.jpi
-rw-r--r-- 1 jenkins jenkins 1413507 May 29 22:37 plugins/blueocean-web.jpi
-rw-r--r-- 1 jenkins jenkins 967614 May 29 22:37 plugins/blueocean-rest-impl.jpi
-rw-r--r-- 1 jenkins jenkins 192974 May 29 22:37 plugins/blueocean-pipeline-api-impl.jpi
-rw-r--r-- 1 jenkins jenkins 66662 May 29 22:37 plugins/blueocean-github-pipeline.jpi
-rw-r--r-- 1 jenkins jenkins 2745123 May 29 22:37 plugins/blueocean-dashboard.jpi
-rw-r--r-- 1 jenkins jenkins 703681 May 29 22:37 plugins/blueocean-personalization.jpi
-rw-r--r-- 1 jenkins jenkins 33137044 May 29 22:37 plugins/azure-sdk.jpi
-rw-r--r-- 1 jenkins jenkins 58121 May 29 22:37 plugins/azure-credentials.jpi
-rw-r--r-- 1 jenkins jenkins 5947031 May 29 22:37 plugins/jira.jpi
-rw-r--r-- 1 jenkins jenkins 28517 May 29 22:37 plugins/display-url-api.jpi
-rw-r--r-- 1 jenkins jenkins 2068729 May 29 22:37 plugins/pipeline-utility-steps.jpi
-rw-r--r-- 1 jenkins jenkins 776815 May 29 22:37 plugins/plugin-util-api.jpi
-rw-r--r-- 1 jenkins jenkins 486809 May 29 22:37 plugins/font-awesome-api.jpi
-rw-r--r-- 1 jenkins jenkins 261324 May 29 22:37 plugins/azure-vm-agents.jpi
-rw-r--r-- 1 jenkins jenkins 957359 May 29 22:37 plugins/credentials.jpi
-rw-r--r-- 1 jenkins jenkins 16099656 May 29 22:38 plugins/analysis-model-api.jpi
-rw-r--r-- 1 jenkins jenkins 226188 May 29 22:38 plugins/mercurial.jpi
-rw-r--r-- 1 jenkins jenkins 54575 May 29 22:38 plugins/blueocean-git-pipeline.jpi
-rw-r--r-- 1 jenkins jenkins 127789 May 29 22:38 plugins/matrix-auth.jpi
-rw-r--r-- 1 jenkins jenkins 34438 May 29 22:38 plugins/pubsub-light.jpi
-rw-r--r-- 1 jenkins jenkins 11342134 May 29 22:38 plugins/warnings-ng.jpi
-rw-r--r-- 1 jenkins jenkins 472289 May 29 22:38 plugins/windows-slaves.jpi
-rw-r--r-- 1 jenkins jenkins 1360650 May 29 22:38 plugins/cvs.jpi
-rw-r--r-- 1 jenkins jenkins 2425761 May 29 22:38 plugins/ec2.jpi
-rw-r--r-- 1 jenkins jenkins 634219 May 29 22:38 plugins/workflow-cps.jpi
-rw-r--r-- 1 jenkins jenkins 839972 May 29 22:38 plugins/timestamper.jpi
-rw-r--r-- 1 jenkins jenkins 1102491 May 29 22:38 plugins/windows-azure-storage.jpi
-rw-r--r-- 1 jenkins jenkins 61490 May 29 22:38 plugins/blueocean-config.jpi
-rw-r--r-- 1 jenkins jenkins 92076 May 29 22:38 plugins/blueocean-bitbucket-pipeline.jpi
-rw-r--r-- 1 jenkins jenkins 23581 May 29 22:38 plugins/blueocean-events.jpi
-rw-r--r-- 1 jenkins jenkins 1057838 May 29 22:38 plugins/blueocean-pipeline-editor.jpi
-rw-r--r-- 1 jenkins jenkins 15198 May 29 22:38 plugins/blueocean-i18n.jpi
-rw-r--r-- 1 jenkins jenkins 8105 May 29 22:38 plugins/blueocean.jpi
-rw-r--r-- 1 jenkins jenkins 308385 May 29 22:38 plugins/github-branch-source.jpi
-rw-r--r-- 1 jenkins jenkins 44276 May 29 22:38 plugins/structs.jpi
-rw-r--r-- 1 jenkins jenkins 96874 May 29 22:38 plugins/workflow-durable-task-step.jpi
-rw-r--r-- 1 jenkins jenkins 35277 May 29 22:38 plugins/kubernetes-credentials.jpi
-rw-r--r-- 1 jenkins jenkins 66978 May 29 22:38 plugins/ansicolor.jpi
-rw-r--r-- 1 jenkins jenkins 99985 May 29 22:38 plugins/groovy.jpi
-rw-r--r-- 1 jenkins jenkins 2337135 May 29 22:38 plugins/configuration-as-code.jpi
-rw-r--r-- 1 jenkins jenkins 189508 May 29 22:38 plugins/script-security.jpi
-rw-r--r-- 1 jenkins jenkins 822801 May 29 22:38 plugins/support-core.jpi
-rw-r--r-- 1 jenkins jenkins 98403 May 30 00:00 plugins/azure-container-agents.jpi
&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>[Resolved] Windows Weekly Package Unavailable</title><link>https://status.jenkins.io/issues/2021-05-25-weekly-windows/</link><pubDate>Tue, 25 May 2021 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-05-25-weekly-windows/</guid><category>2021-05-26T07:51:00-00:00</category><description>&lt;p&gt;Due to a technical issue in the release process, the Windows package for the weekly Jenkins release was unavailable from 2021-05-25 11:30 UTC until 2021-05-26 07:51 UTC.&lt;/p&gt;
&lt;p&gt;A &lt;a href="https://hackmd.io/@jenkins-infra/SJNjA5jKu"&gt;Post-Mortem is available on hackmd.io&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>[Resolved] Nginx ingress upgrade</title><link>https://status.jenkins.io/issues/2021-05-03-maintenance-ingress/</link><pubDate>Mon, 03 May 2021 11:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-05-03-maintenance-ingress/</guid><category>2021-05-04T10:57:00-00:00</category><description>&lt;p&gt;**Update 2021-05-03 11:58 UTC&lt;/p&gt;
&lt;p&gt;The operation is successful, we are now waiting several hours before deleting
the temporary resources that we created during the transition to be sure
that no DNS traffics is redirected to those locations.
We didn&amp;rsquo;t notice service downtime during the process.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-2743"&gt;INFRA-2743&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://hackmd.io/cH4rbENeSOGLHD3rAgnXqQ?both"&gt;NOTES&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There is no ETA at the moment.&lt;/p&gt;
&lt;p&gt;We are upgrading the nginx ingress controllers on the Kubernetes cluster publick8s.
While no down time is expected, the risk during this upgrade is to stop redirecting HTTP/HTTPS traffics to the following services:&lt;/p&gt;
&lt;p&gt;Public services:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;get.jenkins.io&lt;/li&gt;
&lt;li&gt;fallback.get.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;customize.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;li&gt;beta.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;mirror.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;archives.azure.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Private services:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;release.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;infra.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;admin.accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;grafana.publick8s.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The operation consists of deploying temporary ingress controllers listening on ephemeral IPs.&lt;/p&gt;</description></item><item><title>[Resolved] get.jenkins.io disk quota exceeded</title><link>https://status.jenkins.io/issues/2021-04-19-get-jenkins-io-disk-quota-exceeded/</link><pubDate>Mon, 19 Apr 2021 18:50:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-04-19-get-jenkins-io-disk-quota-exceeded/</guid><category>2021-04-19T21:12:00-00:00</category><description>&lt;p&gt;&lt;a href="https://github.com/jenkins-infra/jenkins.io/issues/4270"&gt;Issue 4270&lt;/a&gt;
&lt;a href="https://groups.google.com/g/jenkins-infra/c/olqmLiYBtLo/m/B8BioF6eAAAJ"&gt;Infra mailing list&lt;/a&gt;
&lt;a href="https://docs.google.com/document/d/1bo3YWgacnAbxVw9b9TAzNysYVbR7R24azwTVj0tSJ-4/edit?usp=sharing"&gt;NOTES&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The get.jenkins.io and fallback.get.jenkins.io pods are unable to mount their Azure file storage.
The mount failure prevents the files from being served by get.jenkins.io.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2021-04-19T21:12:00-00:00&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The disk quota issue has been solved using Microsoft &lt;a href="https://docs.microsoft.com/en-us/azure/storage/files/storage-troubleshoot-linux-file-connection-problems#permission-denied-disk-quota-exceeded-when-you-try-to-open-a-file"&gt;documentation&lt;/a&gt;
So mirrorbits containers are back to normal. We tested that service was operational using &lt;a href="https://fallback.get.jenkins.io"&gt;https://fallback.get.jenkins.io&lt;/a&gt;
At the moment, the traffic is still routed to pkg.origin.jenkins.io but it has no impact on the availability of the service.
We will switch back the traffic at a better time.&lt;/p&gt;
&lt;p&gt;We validated that the service was operational using this &lt;a href="https://get.jenkins.io/debian/jenkins_2.288_all.deb?mirrorlist"&gt;mirrorlist&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Jira maintenance</title><link>https://status.jenkins.io/issues/2021-04-15-jira-upgrade/</link><pubDate>Thu, 15 Apr 2021 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-04-15-jira-upgrade/</guid><category>2021-04-15 10:00:00</category><description>&lt;p&gt;The Linux Foundation team that maintains our Jira instance will install a Jira update and operating system updates.&lt;/p&gt;
&lt;p&gt;Maintenance details:&lt;/p&gt;
&lt;p&gt;What:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;issues.jenkins.io
Why:&lt;/li&gt;
&lt;li&gt;upgrade jira to 8.13.5 (latest LTS)&lt;/li&gt;
&lt;li&gt;install OS security updates&lt;/li&gt;
&lt;li&gt;reboot jira instance
Maitenance duration: 1h. Short downtime is expected for 10-20min as we
need to reboot that system&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://groups.google.com/d/msgid/jenkinsci-dev/41268990-aa48-4612-bb71-87d3caf8ed2en%40googlegroups.com"&gt;Discussion&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2021-04-14-maintenance-publick8s/</link><pubDate>Wed, 14 Apr 2021 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-04-14-maintenance-publick8s/</guid><category>2021-04-14T10:00:00-00:00</category><description>&lt;p&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-2944"&gt;INFRA-2944&lt;/a&gt;
&lt;a href="https://hackmd.io/EDpvZx9ZS2GWgHHqWFRDfQ?view"&gt;NOTES&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll do an AKS cluster upgrade.&lt;/p&gt;
&lt;p&gt;The service ldap.jenkins.io service will be restarted.
All other services should remain up and running.&lt;/p&gt;</description></item><item><title>[Resolved] Update sites not updating</title><link>https://status.jenkins.io/issues/2021-03-21-update-sites-not-updating/</link><pubDate>Sun, 21 Mar 2021 10:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2021-03-21-update-sites-not-updating/</guid><category>2021-03-22 12:42:00</category><description>&lt;p&gt;Update sites are currently not updating. Plugin updates released since this outage started are not made available to users.&lt;/p&gt;</description></item><item><title>[Resolved] get.jenkins.io dns update</title><link>https://status.jenkins.io/issues/2020-12-13-get-jenkins-io-dns-update/</link><pubDate>Sun, 13 Dec 2020 13:20:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2020-12-13-get-jenkins-io-dns-update/</guid><category>2020-12-13 14:00:00</category><description>&lt;p&gt;&lt;a href="https://issues.jenkins.io/browse/INFRA-2846"&gt;INFRA-2846&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Because of the previous get.jenkins.io &lt;a href="https://status.jenkins.io/issues/2020-11-12-get-jenkins-io/"&gt;outage&lt;/a&gt;, we temporarily redeployed the service on a virtual machine.
The azure file storage issue is now resolved and the service ready to handle the traffic as it used to be.
I am going to update the dns record to redirect from the temporary virtual machine to our kubernetes cluster.&lt;/p&gt;
&lt;p&gt;No downtime is expected&lt;/p&gt;</description></item><item><title>[Resolved] AKS publick8s version update</title><link>https://status.jenkins.io/issues/2020-12-08-maintenance-publick8s/</link><pubDate>Mon, 07 Dec 2020 13:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2020-12-08-maintenance-publick8s/</guid><category>2020-12-07 14:00:00</category><description>&lt;p&gt;We&amp;rsquo;ll do an AKS cluster upgrade.&lt;/p&gt;</description></item><item><title>[Resolved] get.jenkins.io issues</title><link>https://status.jenkins.io/issues/2020-11-12-get-jenkins-io/</link><pubDate>Thu, 12 Nov 2020 15:54:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2020-11-12-get-jenkins-io/</guid><category>2020-11-14 08:26:00</category><description>&lt;ul&gt;
&lt;li&gt;&lt;em&gt;2020-11-23: Azure is investigating the root cause of the issue&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;2020-11-19: The Azure blog storage is back without additional information&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;*2020-11-14: We temporarily deploy get.jenkins.io outside Azure&lt;/li&gt;
&lt;li&gt;&lt;em&gt;2020-11-17: We have a call with Azure support today&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The network volume used by &lt;a href="https://get.jenkins.io"&gt;get.jenkins.io&lt;/a&gt; is currently down.
This outage affect every services relying on get.jenkins.io like updates.jenkins.io and pkg.jenkins.io&lt;/p&gt;
&lt;p&gt;&lt;a href="https://twitter.com/jenkinsci/status/1326994705230393344?s=20"&gt;Twitter&lt;/a&gt;
&lt;a href="https://groups.google.com/u/1/g/jenkins-infra/c/2eUd_L6bsrM"&gt;Discussion&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Resolved] Maintenance Window</title><link>https://status.jenkins.io/issues/2020-06-13-maintenance-window/</link><pubDate>Sat, 13 Jun 2020 15:54:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2020-06-13-maintenance-window/</guid><category>2020-06-13 16:54:00</category><description>&lt;p&gt;&lt;em&gt;Just began&lt;/em&gt; - We&amp;rsquo;re currently shutting down the network.&lt;/p&gt;</description></item></channel></rss>