www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-6962) Buildbot for Sling
Date Fri, 08 Nov 2013 22:26:17 GMT

     [ https://issues.apache.org/jira/browse/INFRA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gavin closed INFRA-6962.

    Resolution: Fixed
      Assignee:     (was: Gavin)

Thanks Bertrand.

So yeah you've got it, oak tests will only run based on the trunk build passing first, but
if you want to test oak seperatly at any time, using IRC to trigger it is good - or tweak
the settings file.

Feel free to help yourself to sling.conf , just open an issue or ping me on IRC if you get

> Buildbot for Sling
> ------------------
>                 Key: INFRA-6962
>                 URL: https://issues.apache.org/jira/browse/INFRA-6962
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot
>            Reporter: Bertrand Delacretaz
> We'd like to setup a first buildbot build for Sling, and probably expand it to more platforms
and java versions later on. Let me know if you prefer to setup all options right away, but
IIUC we can tweak the settings ourselves once the basics are in place.
> So for now that would be two jobs, on a linux platform, with Java 6 and Maven 3.0.3 or
> Notifications of build status to dev@sling.apache.org
> 1) Full build
> Triggered by commits to the svn URL, maybe at most every N hours.
> svn co https://svn.apache.org/repos/asf/sling/trunk
> cd trunk
> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=256m"
> mvn clean install
> 2) Oak integration tests
> Ideally depends on the previous build, so executed right after it every time.
> svn co https://svn.apache.org/repos/asf/sling/trunk/launchpad/testing
> cd testing
> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=256m"
> mvn clean install -Dsling.run.modes=oak

This message was sent by Atlassian JIRA

View raw message