[jira] [Commented] (SLING-9594) Move Sling builds to ci-builds.apache.org

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161726#comment-17161726 ] 

Konrad Windszus commented on SLING-9594:
----------------------------------------

I requested creation of a folder for Sling in https://lists.apache.org/x/thread.html/rbac05aa7a5b8d00f601d4bd1f2faf655f7f307681bb73f7c39fcbd6a@%3Cbuilds.apache.org%3E

> 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)