Thanks Damien for the confirmation. I'm glad it's not "just me". :)
I can confirm that I can reach updates.jenkins.io again!
Regards,
Fred
On Thursday, May 19, 2022 at 12:18:29 PM UTC+2 damien@gmail.com wrote:
> Hello FredG,
>
> our messages crossed, but yes, the errors on
Hello FredG,
our messages crossed, but yes, the errors on updates.jenkins.io are an un
planned side effect of this change.
We try our best to keep status.jenkins.io up to date (sometime we fail ;) )
but it has the informations.
updates.jenkins.io should be back for you now: can you confirm?
Hello !
As per
https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254
and https://status.jenkins.io/issues/2022-05-19-outage-updates/,
we suffered from a side effect of this change: the DNS record
"updates.jenkins.io" was a CNAME to mirrors.jenkins.io.
As a consequence,
Hi,
Do I assume correctly that this also affects the availability of
ùpdates.jenkins.io`?
I'm having issues connecting to it (e.g. while trying to access the update
center).
Regards,
Fred
On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 damien@gmail.com wrote:
> Hello there!
>
> Reminder
Hello there!
Reminder that we’re going to change the DNS record of `mirrors.jenkins.io`
to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.
Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/
Cheers,
For the infra team,
Damien DUPORTAL
--
You received this message because you are
