On 31/07/2010, at 9:18 AM, Mark Ritchie wrote: > On 30/Jul/2010, at 2:01 PM, Farrukh Ijaz wrote: >> That's why when you know your build is stable, just tag it with a name such >> as something-stable under tags folder in your svn structure. So next time >> you need to produce the same build just checkout the project from tag >> instead of trunk and build it. You will eventually get the same successful >> build. > > That's all good in theory however I have been challenged with the case where > the build system contained states and elements which were not captured by the > repository and thus we were not able to reconstruct a previous built. For > example, what if your WOLips config file had a line commented out before and > you forgot to do it again. Or whatever. > All I'm saying is that from my perspective, it might be useful to have a copy > of the build product. It might not too. ;-)
Yep, the tools change over time and it may produce the build differently in future. However, storing binary builds in svn (or similar) makes for a svn repo and checkout + presumably duplication of all the dependent jars/frameworks (if each of your apps was in a different svn repo, for example) Of course, this is not a problem -- but just throwing maven out there as an alternative, which means: - one repo with all historical builds and dependencies. So support team can easily browse/download versioned builds as necessary without searching through source code history. - small(er) source code: without duplicate jars/frameworks but just the id refs for them. with regards, -- Lachlan Deck _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
