Hello, A quick update: as the ACI outage seems to be gone, we've reverted the patch which forced usage of VM for Windows agents.
Build requesting Windows container agents are now back to using ACI Damien, for the Jenkins infra team Le mardi 14 janvier 2025 à 16:59:00 UTC+1, Damien Duportal a écrit : > Hi dear contributors, > > The outage on Azure is still there. Despite their service health status > being all green, creating Windows containers is randomly (and quite often) > failing with no obvious error. > > We've updated status.jenkins.io, we are working on adding a ci.jenkins.io > banner to spread the information, and we started discussing a "hard" > implementation change. > > Damien, for the Jenkins infra team > > Le lun. 13 janv. 2025 à 18:12, Damien Duportal <damien....@gmail.com> a > écrit : > >> Hello dear contributors, >> >> The outage is finished since the 10 January around 20:30 UTC as described >> in >> https://github.com/jenkins-infra/helpdesk/issues/4490#issuecomment-2587690388 >> . >> >> We realized that the "fallback" technique to Windows VM agents did not >> work as expected: we have fixes in progress described in the issue this >> kind of issue in the future. >> >> We are sorry for the inconvenience, >> >> The Jenkins Infra team >> >> Le ven. 10 janv. 2025 à 12:57, Damien Duportal <damien....@gmail.com> a >> écrit : >> >>> Hello dear contributors, >>> >>> There is an ongoing Azure network outage which impacts the builds using >>> Windows container agents on ci.jenkins.io. >>> >>> More details in >>> https://status.jenkins.io/issues/2025-01-08-ci.jenkins.io-azure-outage/ >>> >>> Given the context (It took more than 24h for Microsoft to notice the >>> issue, it also took 24h for the Jenkins infra team to notice this due to >>> team unavailability), we recommend that you use Windows VM agents instead >>> (see ci.jenkins.io banner) for the time being. >>> >>> We shouldn't expect a full recovery until Monday as per Microsoft >>> communications. >>> >>> Many thanks to Jesse Glick, TIm Jacomb and Bruno Verachten for reporting >>> the issue >>> >>> Damien Duportal, for the Jenkins Infra team >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/VQcRiUYu92o/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> jenkinsci-de...@googlegroups.com. >>> To view this discussion visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/c8653b6a-0fa9-4552-9875-9bd4e071d4d2n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/c8653b6a-0fa9-4552-9875-9bd4e071d4d2n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/99f52b4d-363d-4fae-9339-f9762de9dd5fn%40googlegroups.com.
