Hello, In order to access https://release.ci.jenkins.io, you now need to use the new private VPN private.vpn.jenkins.io
To do so, if you already have access to the existing VPN, fill an help desk issue explaining why you need access to release.ci.jenkins.io If you don't already have access to the existing VPN, follow the instructions given at https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access, and mention why you'll also need access to release.ci.jenkins.io Regards, Hervé for the Jenkins Infrastructure Team On Thu, Mar 23, 2023 at 12:20 PM Herve Le Meur <[email protected]> wrote: > Hello, > > We'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. > > 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's done. > > 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't allow access to this new cluster and thus the next location of > release.ci.jenkins.io. > We'll send further instructions for this by email. > > More information and detailed migration plan: > https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1463863691 > > Regards, > > Hervé for the Jenkins Infrastructure team > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAL-Lwjykb5DPVSCPs_9MU18eK%2BQGejpMuA3N1_QpJH6XQg6UeQ%40mail.gmail.com.
