[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944795#comment-14944795 ] Robert Munteanu commented on SLING-3234: Yes, we do have Sling build running on Jenkins - https://builds.apache.org/view/S-Z/view/Sling/ . I am not sure about the state of the buildbot jobs > 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 >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. > 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)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944803#comment-14944803 ] Bertrand Delacretaz commented on SLING-3234: We were having trouble with the buildbot jobs and Jenkins got better, so we have ignored the buildbot lately. > 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 >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. > 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)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944202#comment-14944202 ] oliver.burkhalter commented on SLING-3234: -- Is it correct that the current Sling builds are running on Jenkins as documented here: SLING-920? > 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 >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. > 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)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087316#comment-14087316 ] Bertrand Delacretaz commented on SLING-3234: The INFRA-8098 svn issues haven't gotten better, still no usable builds at http://ci.apache.org/builders/sling-trunk 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 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. 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.2#6252)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14033593#comment-14033593 ] Bertrand Delacretaz commented on SLING-3234: I have added the mvn -fae option to https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/sling.conf to avoid aborting the build if a single test fails 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 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. 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.2#6252)
[jira] [Commented] (SLING-3234) Sling buildbot continuous integration
[
https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13857557#comment-13857557
]
Bertrand Delacretaz commented on SLING-3234:
http://ci.apache.org/builders/sling-trunk-oak/builds/64 has failed with
something that looks like an infrastructure problem - for now, just making a
note of it in case that happens again.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install)
on project org.apache.sling.settings: Failed to install metadata
org.apache.sling:org.apache.sling.settings:1.3.1-SNAPSHOT/maven-metadata.xml:
Could not read metadata
/home/buildslave21/.m2/repository/org/apache/sling/org.apache.sling.settings/1.3.1-SNAPSHOT/maven-metadata-local.xml:
input contained no data - [Help 1]
{code}
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
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.
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.1.5#6160)
