Thanks for the heads up, Mark! I should've checked into Jenkins IRC channel 
before reaching out.
Our use case is that we use it as a failover when our corporate firewall 
gets a little aggressive on blocking the redirects to some other mirrors. 
Trusty archives was always there, but I'll look into unblocking couple of 
other mirrors with our security overlords.
Cheers & happy holidays!

On Tuesday, December 22, 2020 at 2:23:43 PM UTC+1 Mark Waite wrote:

> Do you have a specific use case that is harmed by the downtime of 
> archives.jenkins-ci.org?  In general, the current content of that machine 
> is mirrored in at least 6 different locations around the world as shown by 
> https://get.jenkins.io/war/2.271/jenkins.war?mirrorlist
>
> On Tuesday, December 22, 2020 at 6:21:03 AM UTC-7 Mark Waite wrote:
>
>> No need to contact anyone.  We know it is down and will work on it after 
>> the holidays.
>>
>> It was noted last week in the Jenkins IRC channel that the machine is 
>> offline.
>>
>> On Tuesday, December 22, 2020 at 6:04:54 AM UTC-7 pashc...@gmail.com 
>> wrote:
>>
>>> Howdy,
>>>
>>> From the Jenkins mirrors status page 
>>> <http://mirrors.jenkins-ci.org/status.html> it looks like 
>>> http://archives.jenkins-ci.org has been down for almost a week now. 
>>> Does anyone know who should be contacted for its outage (fully understand 
>>> that it might be holiday & vacation related and that there are no SLAs 
>>> around its uptime).
>>> Jenkins Mirrors page <https://www.jenkins.io/download/mirrors/> talks 
>>> about Oregon State University Open Source Lab mirroring it - do I just 
>>> email their support via sup...@osuosl.org? 
>>>
>>> Happy holidays to y'all!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f0e74eb5-5537-45c9-9abf-fbcb64e692c4n%40googlegroups.com.

Reply via email to