[p4] Build automation question

[Jay Renbaum]

Thanks for the input. We went with Parabuild in the end. Inexpensive and
does what we need. I agree with other comments, the docs could be
re-written in English. Otherwise we are happily building. I am able to
run manual builds from Parabuild that take changelist numbers and branch
names as input and pass this info to my build script which takes care of
the rest. This in necessary to build outside of Parabuild's relative
path since it can't sync to mixed branches and non-tip revisions easily.

Jay

-----Original Message-----
From: steve at vance.com [mailto:steve at vance.com] 
Sent: Wednesday, January 17, 2007 12:18 AM
To: Jay Renbaum
Cc: perforce-user at perforce.com
Subject: Re: Build automation question

Have you looked at your open source options like CruiseControl, 
DamageControl and Maven? 

Steve 

Jay Renbaum writes: 

> Does anyone have suggestions for a build automation tool that works
well
> with Perforce? 
> 
>   
> 
> I've been looking at Parabuild, Pulse and Quickbuild, but they are all
> limited in their functions. I would like to find a tool that can
perform
> continuous builds for us, but is also capable of accepting changelist
> inputs when kicking off a build. 
> 
>   
> 
> Additionally, we build out of 2 depots that reside under a single
> Perforce server. This means that we have one changelist counter that
> keeps growing across all depots. We actually create workspaces on the
> fly. My current homebrew build script accepts different branch names
for
> the 2 components and 2 different changelists as one component may be
at
> a different point in development than the other. Is anyone aware of a
> build tool that allows for different branches and/or changelists?  
> 
>   
> 
> Thanks, 
> 
>   
> 
> Jay Renbaum 
> 
>   
> 
>   
> 
>   
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user