Skip to content

Jenkins Mirror Plan: configuration change #29

Description

@dduportal

Hello dear OSSPlanet team!

The Jenkins project is very grateful for your sponsoring in the form of a download mirror (rerequest in #26)!

The Jenkins infrastructure team is doing some changes and we would want you to:

  • Change the source of the rsync data sync from OSUOSL (rsync://ftp-nyc.osuosl.org/jenkins/ or rsync://ftp-chi.osuosl.org/jenkins/ as we specified in [OSSPlanet] Jenkins Project Application for Mirror Plan #26) to our own Jenkins reference server rsync://archives.jenkins.io/jenkins)
    • The rsync server on archives.jenkins.io is unauthenticated, IPv4 and IPv6 compliant, located in Europe and all hosts are allowed for now.
  • Share with us the public outbound IPs of your rsync system so we can add you to the allow list of the archives.jenkins.io VM.
    • If you have an API endpoint (like the GitHub meta API) with this IP, we can automate the IP retrieval/update on our own once a day/week
    • If you want to share privately these values: jenkins-infra-team googlegroups.com is our private internal mailing list

For context (and trust in this request), here is the issue with details about this change: jenkins-infra/helpdesk#4653.
TL;DR; we are improving the Jenkins (and its plugins) release process to control the references.
Since archives.jenkins.io is the default (active) fallback for Jenkins download mirrors system, we want to use it as reference so we decouple from OSUOSL servers.

Thanks in advance!

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions