[INFRA-3125] Migrate jenkins-infra repositories from branch "master" to "main"

[jenkins-infra-bot]

For some of them we'll have to create the "main" branch, keep the "master" one, update dependant pipelines, then remove "master"

---

Originally reported by hlemeur, imported from: Migrate jenkins-infra repositories from branch "master" to "main"

• status: Open
• priority: Minor
• resolution: Unresolved
• imported: 2022/01/10

[dduportal]

Update: jenkins-infra/ldap is next (ref. #3837 (comment))

[dduportal]

Update: https://github.com/jenkins-infra/mirror-scripts

[lemeurherve]

Update:

• https://github.com/jenkins-infra/infra-reports
• https://github.com/jenkins-infra/uplink

[lemeurherve]

Update: https://github.com/jenkins-infra/javadoc

[NotMyFault]

Update: https://github.com/jenkins-infra/plugin-site

[lemeurherve]

Update: jenkins-infra/crawler#143

[debx4]

is this issue open ?
I like to contribute on this issue if this is still opened .

[dduportal]

is this issue open ? I like to contribute on this issue if this is still opened .

Hi @debx4 , yes it is still open but contribution like these are not easy ones as it often requires a lot of changes (and besides, requires presence of a maintainer to perform the effective branch change in the repository).

I think jenkins-infra/pipeline-library could be a good candidate though:

• No strong reason to keep the name master
• But a lot of tiny changes across repositories to make it a valuable contribution.

Be aware you'll have to search for the master branches references (as this issue requires some discovery and works in autonomy)