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

Robert Munteanu commented on SLING-3234:
----------------------------------------

As discussed on [dev@sling: \[ci\] Retire 
buildbot?|https://lists.apache.org/thread.html/ca3a5ca1e72225e929a99acf8553f0e8bf00330acc58c137faef2ce6@%3Cdev.sling.apache.org%3E],
 I asked infra to remove the two sling builders

> Sling buildbot continuous integration
> -------------------------------------
>
>                 Key: SLING-3234
>                 URL: https://issues.apache.org/jira/browse/SLING-3234
>             Project: Sling
>          Issue Type: Task
>          Components: Testing
>            Reporter: Bertrand Delacretaz
>
> Buildbot jobs have been setup for Sling in INFRA-6962;
> * http://ci.apache.org/builders/sling-trunk (triggered by commits)
> * http://ci.apache.org/builders/sling-trunk-oak (runs after sling-trunk)
> We'll use this issue to keep track of changes related to this buildbot setup, 
> as we did with SLING-920 for our Jenkins builds.
> I suggest marking issues that cause intermittent buildbot failures as 
> blockers for this issue, so that we can quickly check if failed builds are 
> due to known issues.
> Builds can be started manually via IRC if needed, via #asftest. Talk to the 
> sling-bot there, start with "help force", "status" or "commands".
> [1] 
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/sling.conf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to