Does that mean we should release plug-ins to repo.jenkins-ci.org instead of maven.jenkins-ci.org now?
Ulli On 03/01/2012 04:11 AM, Kohsuke Kawaguchi wrote: > > We've been using http://maven.glassfish.org/ for resolving all the > artifacts for building core and plugins. But it has been down for the > past two days and we have no ETA. > > So I propose we switch to http://repo.jenkins-ci.org/public. > > > This issue was raised several times in the past that we rely on a 3rd > party repository we have on control over. It was simply an inertia > from earlier days when I was in the Glassfish team (and even had the > physical access to the system!), and the migration never really came > high enough in the priority list, until this outage. > > http://repo.jenkins-ci.org/ is a hosted Artifactory, operated by > JFrog. They kindly let us use their service for free (thanks JFrog!) > It was started several weeks ago after a discussion in the project > meeting, and the original motivation was to migrate from self-managed > http://maven.jenkins-ci.org/ > > That migration work is still in the proof-of-concept phase, and more > on that in the upcoming project meeting, but in the mean time, we can > and we should fast-track maven.glassfish.org migration since it has a > bigger impact on our development. > > The core and super POM have already been modified to use this new > repository, and it works well. The plugin parent POM will have this > new location starting 1.453, but if you depend on earlier parent POMs, > you can specify the following fragment in your plugin POM to make this > resolve: > > <repositories> > <repository> > <id>repo.jenkins-ci.org</id> > <url>http://repo.jenkins-ci.org/public/</url> > </repository> > </repositories> > > <pluginRepositories> > <pluginRepository> > <id>repo.jenkins-ci.org</id> > <url>http://repo.jenkins-ci.org/public/</url> > </pluginRepository> > </pluginRepositories> > > > Also, adding the following fragment to your ~/.m2/settings.xml will > make your Maven use the new repository whenever m.g.o-public is > referenced. > > <settings> > <mirrors> > <mirror> > <id>repo.jenkins-ci.org</id> > <url>http://repo.jenkins-ci.org/public/</url> > <mirrorOf>m.g.o-public</mirrorOf> > </mirror> > > This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes > belly up tomorrow, we just need to make a few DNS/redirect adjustments > to be able to keep this new URL working. So this should be the last > time we need to make this kind of migration. > > >
