[p4] Deployment files in Perforce or Maven?

[vegard.setrenes@telenor.com]

Thank you all for answering! It will be valuable input for making a decision :)

- Vegard

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> steve at vance.com
> Sent: Tuesday, January 09, 2007 6:11 PM
> To: perforce-user at perforce.com; perforce-user at perforce.com
> Subject: Re: [p4] Deployment files in Perforce or Maven?
> 
> The Maven repository is not a bad way to go if you don't care 
> about version
> issues or if you have your dependencies versioned properly.
> 
> In general I shy away from checking in binary derived 
> objects, EXCEPT when
> using Perforce to bootstrap environments or as a deployment 
> mechanism. I
> think it's perfectly reasonable to check in those kinds of 
> artifacts for
> release builds for distribution and deployment purposes.
> 
> As for the "last N" question, there was a paper presented by 
> Richard Baum
> at the last Perforce User Conference addressing this issue. 
> Beware that
> this is a somewhat dangerous operation that you use at your 
> own risk. It
> was presented more to push the boundaries of what can be 
> accomplished with
> Perforce scripting than as a suggestion of something you should do in
> production. That said, several people have gotten good 
> mileage from it.
> 
> Steve
> 
> Original Message:
> -----------------
> From:  vegard.setrenes at telenor.com
> Date: 	Tue, 9 Jan 2007 12:46:35 +0100
> To: perforce-user at perforce.com
> Subject: [p4] Deployment files in Perforce or Maven?
> 
> 
> Hi,
> 
> In my department we use Perforce on all Java development, and 
> we have been
> following the "best practice" of not storing anything in the 
> depot, other
> than what's necessary to do a build. In other words, we don't check in
> binary archive files like EARs and JARs.
> 
> The source code for one of our systems was imported from cvs 
> one year ago.
> We have some deployment scripts that depend on retrieving 
> EARs and JARs
> from dedicated deployment directories in the same old cvs. 
> These scripts
> copy the deployment files to multiple test or production servers.
> 
> To be able to finally get rid of the cvs base, we are looking 
> for the best
> way of keeping the deployment files. Should we use Perforce 
> or a web based
> Maven repository?
> 
> It is clear that we do not need all historic revisions of the 
> files. We are
> just looking for a good way to make them available for the automated
> deployment scripts. So I guess we could specify the +S modifier for a
> designated part of the Perforce depot. But ideally there 
> should be a way to
> keep just the N last revisions, making it possible for the deployment
> scripts to do rollbacks. Is this possible without using the obliterate
> command?
> 
> How do you organize your deployment files in your organization?
> 
> Thanks,
> 
> - Vegard
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>