[p4] Build automation question

[Jeff Jensen]

Did you look at CruiseControl?  I brought in both Perforce and CruiseControl
at my current customer, and they work very well together.

To handle the different versions, I suggest using some type of artifact
repository that the component under build uses for its dependencies.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jay Renbaum
Sent: Tuesday, January 16, 2007 1:32 PM
To: perforce-user at perforce.com
Subject: [p4] Build automation question

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