[p4] Perforce and Apache

[Qazwart]

You could put just compile information in Ant, but then you'd have to  
write shell scripts to do checkout and updates. Or you could do it in  
CruiseControl, but then you'd have to update your CruiseControl  
configuration file.

Somewhere, if you are automating your build process, you'll have to  
include checking out and updating your source, and somewhere, you'll  
have to tie this to your source control system.

The best advice is to try to keep things as modular as possible. For  
example, in your Ant script, make the checking out and updating, and  
labeling of your source code as separate targets from your compile  
and deploy targets. I would also try to centralize the checkout and  
label targets in a single build.xml script that can be included in  
other Ant scripts via an "ant" call or in a <include> task. That way,  
when you do change your version control system, your changes are  
limited in one or two places and not sprinkled through out your build  
system.

I prefer to keep my checkout, label, update, and commit tasks in my  
Ant script. That way, my entire build process is in the Ant script,  
and I don't have any shell script to worry about. My developers can  
run the same Ant script I use and know if it works for them, it will  
work when I do the official build.

I wonder how Mavin handle all of this?

On Mar 24, 2007, at 3:25 PM, Dave Lewis wrote:
> just an opinion, but I wouldn't put any perforce or vss or source  
> control stuff into ant etc. Those tools are for building and should  
> not be strongly tied to the source control system. That makes  
> switching source control much easier, and also makes stuff like  
> escrow (and the possibility of escrow builds) much easier.
>
> I usually surround the build task with an scm shell that takes care  
> of getting the right source, then the build stuff just builds it.
>
> I'm sure there are lots of reasons to do it otherwise...
>
>
> dave
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

David Weintraub
david at weintraub.name
qazwart at gmail.com