[p4] storing builds (was Nant Build Question)

[Chuck Emary]

Hello,
We use two servers to separately store our binaries and source code.
Our CI builds never get artifacted.  Our nightly builds do get
artifacted, into Perforce folders called latest.  Developers wanting
needing bleeding edge pull from there.  Code that is deemed "stable" is
promoted, via the build process, into Perforce folders called stable.

Release binaries are also stored.  The benefit to us here has been that
it making patching through the MS MSI/install mechanism very easy, at
least that's what thee install guys tell me.  Essentially you pull down
the binaries, replace some of them with the new binaries and the MSI
stuff then creates a patch with the deltas.  Patching used to be a
painful process for us, and has now become very straight forward with
this process.

I have not automated cleanup of the binary server.  I have to
periodically clean it up with deletes and obliterates, which usually
consumes an entire Saturday, even using scripts.  We typically have 2 TB
worth of binaries stored.

Hope the data points are useful to someone, have a good one.



-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Jensen
Sent: Thursday, September 21, 2006 6:37 AM
To: 'Perforce Users'
Subject: Re: [p4] storing builds (was Nant Build Question)

Another option for storing/sharing build artifacts is with a build tool
such
as Maven that has its own "repository" feature.  Maven can place all
desired
build artifacts in its repo for sharing/storing (very handy for the
build
process - declare dependencies and it resolves them from the repo).
Users
can submit any particular version needed to the SCM.

We do this combined approach and it is nice - keeps the Perforce size
and
cleanup tasks down but stores what we want (e.g. specific releases),
while
allowing our CI and nightly builds to remain available until we purge
them
from the Maven repo.

This could be a happy medium for some between the "store none" and
"store
all" - store some in SCM and the temporary minutia in the repo.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
Sent: Wednesday, September 20, 2006 1:52 PM
To: Perforce Users
Subject: Re: [p4] storing builds (was Nant Build Question)



> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of Dave Lewis
> 
> BUT, I really think checking them into a completely different server 
> from the source code is a good idea!  I kind of want to do that with 
> our stuff now. (or not check them in at all!)

I tend to agree with the separate server idea. Failing that, at a
minimum, I
would check them into a depot of their own.

-Wm 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user