You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/10/14 09:20:20 UTC
[jira] [Resolved] (SLING-3234) Sling buildbot continuous
integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-3234.
------------------------------------
Resolution: Later
Resolving as 'Later' after disabling the sling builders from buildbot.
We can always reopen if we decide to re-activate the buildbot.
> 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)