[SLING-9594] Move Sling builds to ci-builds.apache.org

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Component/s: Build and Source Control
• Assignee: Unassigned
• Reporter: Robert Munteanu
• Created: 20/Jul/20 12:48
• Updated: 24/Aug/20 17:36
• Resolved: 18/Aug/20 21:27

Description

The ASF Jenkins infrastructure is moving to to a new
Cloudbees based Client Master called https://ci-builds.apache.org, see https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E . The migrations of all jobs needs to be done before the switch off date of 15th August 2020, so we have a maximum about three weeks from now to make the move.

There is no automatic way of migrating the jobs, but thankfully our current set up is very much automated and reasonably well documented at https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup .

It very well may be that we can simply set up another GitHub org on the new Jenkins master, provide the secrets and be done with it. But it needs investigation though.

Issue Links

• is related to: SLING-9651 Committer CLI release checks should use ci-builds.apache.org
• is related to: SLING-8704 Build PRs from non-committers
• is related to: SLING-9686 Update project badges to point to ci-builds.apache.org
• is related to: SLING-9652 Parent: Add ci-management to parent pom