Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <15009132.post@talk.nabble.com>
Date: Mon, 21 Jan 2008 15:27:49 -0800 (PST)
From: dhpeterson <dhpeterson@gmail.com>
To: buildr-user@incubator.apache.org
Subject: Re: Continuous Integration
In-Reply-To: <3de5d7d20801211001l17de3e9al7a36b66107da50fa@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <0546C070E195354E9CF31C68660E64B603C7E8@EXCHANGE2.mentiscorp.com>
 <AFA13AD9-63B7-41DB-9BA3-032CA029B416@detailedbalance.net>
 <3de5d7d20801171736k2f63e2aqa1c58c4a9afe1d78@mail.gmail.com>
 <14988186.post@talk.nabble.com>
 <3de5d7d20801211001l17de3e9al7a36b66107da50fa@mail.gmail.com>


Hi Assaf,

Attached is a first-cut recipe for Bamboo setup with Buildr. It is very
straightforward. Feel free to edit prior to inclusion in recipes. (I won't
be offended!)

It can be difficult to draw the line between Bamboo configuration and
Buildr-Bamboo configuration, so the below recipe is a minimal complete
configuration to a buildr project get up and running. Some sections such as
SCM configuration are omitted for brevity.

Dave

====

Bamboo Buildr Recipe


This recipe outlines how to configure a new Bamboo project to use Buildr.
The following steps assume that you have logged-on to Bamboo as an
Administrator.


 1. Configure a Builder

 * Select the Administration tab from the Bamboo toolbar.
 * Select the Builders area (first option) from the Administration menu.
 * Using the Add Builder dialog, configure a custom builder for Buildr with
the following options:
   - Label: buildr
   - Type:  Custom Command
   - Path:  /path/to/buildr (typically "/usr/bin/buildr")


 2. Create a Plan

 * Select the Create Plan tab from the Bamboo toolbar to enter the Create
Plan wizard.
 * In "1. Plan Details", define your build plan including project name,
project key, build plan name and build plan key.
 * In "2. Source Repository", specify your source code repository settings
(CVS or SVN).
 * In "3. Builder Configuration", specify the "buildr" builder that you
defined above, along with the following:
   - Argument: "test=all" (ensures that all tests are run even if failures
are encountered)
   - Test Results Directory: "**/reports/junit/*.xml" (or your path to test
results, if different).
 * The remaining wizard sections may be either skipped or configured with
your preferred settings.
 
 
 3. Trigger a Build
 
  A build should occur automatically at the point of project creation. It
can also be manually triggered at any time 
 
  * Navigate to the project summary page (located at:
http://YOUR_BAMBOO_URL/browse/PROJECTKEY-YOURPLAN).
  * Click on the small arrow to the left of the label "Build Actions"
  * Select "Checkout and Build" from the pop-up menu to force a build.

The project page will contain full status information for previous builds
and the results tabs will integrate the results from your JUnit tests.

===


Assaf Arkin wrote:
> 
> On 1/20/08, dhpeterson <dhpeterson@gmail.com> wrote:
>>
>>
>> Assaf Arkin wrote:
>> >
>> > Any of you using Buildr with continuous integration, can you share
>> details
>> > about setup, configuration, special tricks, etc?
>> >
>> > We're going to have a section for documenting recipes in the next
>> release,
>> > and I'd like to include that.
>> >
>> > Assaf
>> >
>> >
>>
>>
>> Hi Assaf,
>>
>> We're running Atlassian Bamboo here with Buildr and it works just fine. I
>> just added a build type for buildr, pointed it to the local svn repo, and
>> set the junit XML report path and everything worked out of the box.
>>
>> I've also played with buildr under continuum which also works, but is a
>> bit
>> more painful to setup.
>>
>> I'd be happy to contribute recipes / help for this section of the docs.
> 
> 
> Thanks.
> 
> What I'm thinking is two to five paragraph of the steps necessary to set
> it
> up in the UI, or setup properties/configuration, basically if you had to
> do
> it again on a fresh install.  One trick worth mentioning is adding
> test=all
> on the command line, so it doesn't stop on the first failure, another
> pointing to the project's junit/report directory.
> 
> Probably easiest to just send it to the list, so anyone can read, and I'll
> pull it into the recipes page.
> 
> Assaf
> 
> Dave
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Continuous-Integration-tp14937657p14988186.html
>> Sent from the Buildr - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Continuous-Integration-tp14937657p15009132.html
Sent from the Buildr - User mailing list archive at Nabble.com.