archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pankaj Tandon <pankajtan...@gmail.com>
Subject Re: Using archiva for setting up a corporate dev environment
Date Mon, 31 May 2010 20:55:26 GMT

Hi Wendy,
Thanks for your response. Yes, the Staging repo concept in Nexus is similar
and certainly a more robust way to manage what get's into the production
repo. However, Nexus Pro costs $$ and we are not yet ready to fork out the
money :)
So what we are doing is similar but it is controlled via a plugin. It works
without the web-ui or roles.
As far as controlling each artifact is concerned, it can be a challenge if
you have to deal with approval on a per-project basis. But when you have
only one (or a few) projects, it's not so bad.
It's more of a brute-force approach:
1. Build in dev using any artifacts by allowing downloads from the net.
2. Throw over to a prod build environment and build against the monitored
repo (by switching to a different settings.xml pointing to the prod repo
group). If artifacts are missing in the prod repo, then the plugin will tell
you what is missing and will give the operator the chance to move artifacts
to prod repo. If nothing is missing, then there's nothing to do and life is
good.

It's simple and effective.

Thoughts are welcome!
Pankaj




Wendy Smoak-3 wrote:
> 
> On Sat, May 29, 2010 at 10:37 AM, Pankaj Tandon <pankajtandon@gmail.com>
> wrote:
>> I posted my experience in using Archiva as a Repository manager for
>> setting
>> up a corporate development environment here:
>> http://nayidisha.com/techblog/using-archiva-for-setting-up-a-corporate-development-environment
> 
> Nice work, thanks!
> 
> How do you control what gets into production builds?  Having the
> remote repos separate is good, but once things get into the local
> repository, they are available to any build.
> 
> Also, are you really able to get a binary "approved" or "not approved"
> decision on every artifact?  IME it's more complex than that, and an
> artifact may be approved for one team/application but not for another.
> 
> (You might want to take a look at the discussion about repository
> staging and promotion on the developers list.  It should allow you to
> copy artifacts from one repo to another through the Web UI.  It's
> intended to stage and promote a release, so I'm not sure this use case
> would be covered initially, but it's a similar concept.)
> 
> -- 
> Wendy
> 
> 

-- 
View this message in context: http://old.nabble.com/Using-archiva-for-setting-up-a-corporate-dev-environment-tp28716372p28734999.html
Sent from the archiva-users mailing list archive at Nabble.com.


Mime
View raw message