RE: How to avoid cluttering the svn repository with several versions of compiled files

From: Stephen Connolly [mailto:stephen.alan.connolly_at_gmail.com]
Sent: Friday, May 15, 2009 7:48 AM
To: David Weintraub
Cc: Les Mikesell; Bolstridge, Andrew; users_at_subversion.tigris.org; brianf_at_apache.org; Jason van Zyl
Subject: Re: How to avoid cluttering the svn repository with several versions of compiled files

2009/5/14 David Weintraub <qazwart_at_gmail.com>
> David Weintraub wrote:
>> We use both Hudson and Nexus. Hudson is our continuous build engine,
>> and we store the daily builds on Hudson, and depending upon the
>> project, we store either the last 20 builds or at least three months
>> worth of builds(which ever is greater). Developers and QA simply
>> retrieve the builds they want from Hudson.

On Thu, May 14, 2009 at 1:21 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> Can you comment on how it might work for non-java projects?  For example,
> common libraries for other c or c++ projects or deployable executables -
> probably would be managed by Hudson, though.

I took a quick look at Nexus and it does seem to be relatively tightly integrated with Maven, but there are others - Alfresco seems quite good, or KnowledgeTree, or Nuxeo (which lists a load of media awards)

It'd be ironic if any of them used SVN as a back-end data storage module :)

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2268466

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-15 11:00:31 CEST