[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Stephen Connolly <stephen.alan.connolly_at_gmail.com>
Date: Fri, 15 May 2009 07:48:22 +0100

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

CCing Jason and BrianF,

FYI, you can also use Maven tasks for ANT to deploy to nexus...

you can also deploy via HTTP... it may be as simple as a POST or else it's
WEBDAV... you'd have to look into it... or ask Jason/BrianF ;-)

Additionally, AFAIK there are other repository layouts supported by Nexus,
and you might not even have to follow the Maven repository layout... you'd
have to look into it... or ask Jason/BrianF ;-)

-Stephen

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-15 08:49:26 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.