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

> 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.

Nexus can store almost any binary type file, so storing executables
shouldn't be a problem. The big issue is adopting the Maven naming
conventions for releases. For example, you have a program called
Foo.exe. Maven puts the release number in the file name, so it will
become Foo-1.2.3.exe.

The two issues would be adding a file into the Nexus repository and
retrieving a file from the Nexus repository.

To add a file you can use the Nexus web interface to add a file, or
you can use the Maven deploy:deploy-file "mojo". That way, when you
build a DLL or .so, you can automatically deploy it into Nexus. We do
this via a shell script.

To retrieve a file from Maven requires either curl or wget, both open
source tools available for Mac, Windows, or Linux. If you're using
Make, you could define a default rule that fetches the library from
the Nexus repository.

There's probably better tools out there for non-Maven type tasks, but
since we use Nexus anyway, adopting it for other non-Maven projects
simply made sense.

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2261553
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].