Re: [hudson-dev] Hudson on hudson and local nexus?

[Henrik Lynggaard Hansen <henrik@xxxxxxx>]

2012/4/19 Manfred Moser <manfred@xxxxxxxxxxxxxxxx>:
> That would just replace one repo with another repo that could fail. You
> should figure out which artifacts are not on central that are needed by
> the build and get these there and then get rid of the dependency on the
> glassfish repo.
>
> Last time I tried that it was only one unit testing related library ..

After I mirrored glassfish to central things seem to be pretty much
building, although not having a local nexus leaves me with two hurdles

1) Some plugins (one at the current time) require closed sourced
artifacts which arent't available in open repositories

2) My initial intent with the Hudson on Hudson was to test the
upcomming (snapshot) versions of plugins¨, and for that to work I
would need to push them to a alternative snapshot repo, since neither
the hudson nor jenkins snapshots seem to be available online. I need
that because I don't have a shared local repo, and I think
eclipse/sonatype aether only does version range lookup to remote
repos.

The intention was to in time extend HonH to also build some of the
jenkins plugins which we have included in the automated testing. And I
have seen some jenkins plugins which needs more exsotic dependencies
which are not in central, and I have been using my local nexus to
cleanup and route around the jenkins public group

Maybe the ambition I had is not worth the trouble of a local nexus?