[ https://issues.apache.org/jira/browse/SLING-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166271#comment-17166271 ]
Bertrand Delacretaz edited comment on SLING-9594 at 7/30/20, 1:22 PM: ---------------------------------------------------------------------- We'll also have to update the build badges links [1] {{find . -type f | grep -i readme | xargs grep //builds.apache.org}} currently finds 298 readme files in my local workspace. [1] like https://builds.apache.org/buildStatus/icon?job=Sling/sling-org-apache-sling-installer-provider-installhook/master _Update: Gavin said on the builds list that "builds.a.o will redirect to ci-builds.a.o to allow for bookmarks/favourites/documentation etc to follow to the new uri" so we might not need this._ was (Author: bdelacretaz): We'll also have to update the build badges links [1] {{find . -type f | grep -i readme | xargs grep //builds.apache.org}} currently finds 298 readme files in my local workspace. [1] like https://builds.apache.org/buildStatus/icon?job=Sling/sling-org-apache-sling-installer-provider-installhook/master > Move Sling builds to ci-builds.apache.org > ----------------------------------------- > > Key: SLING-9594 > URL: https://issues.apache.org/jira/browse/SLING-9594 > Project: Sling > Issue Type: Task > Components: Build and Source Control > Reporter: Robert Munteanu > Priority: Critical > > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)