[
https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830010#comment-13830010
]
Bertrand Delacretaz edited comment on SLING-3234 at 11/22/13 2:47 PM:
----------------------------------------------------------------------
The sling-trunk build correctly starts after commits now, with a 2 minutes wait.
The sling-trunk-oak build runs if the sling-trunk build is successful.
I have edited the sling.conf to move the sling-bot to the #sling IRC channel,
it's not on #asftest anymore.
was (Author: bdelacretaz):
The sling-trunk build correctly starts after commits now, with a 2 minutes wait.
I have edited the sling.conf to move the sling-bot to the #sling IRC channel,
it's not on #asftest anymore.
> Sling buildbot setup
> --------------------
>
> Key: SLING-3234
> URL: https://issues.apache.org/jira/browse/SLING-3234
> Project: Sling
> Issue Type: Task
> Components: Testing
> Reporter: Bertrand Delacretaz
> Assignee: 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.
> 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.1#6144)
