Monday morning I came into work and discovered that I cannot commit to the Hudson Subversion repository. Initially I wasn’t worried â€” I thought it was just another java.net outage that will resolve itself in a few hours â€” but a little research a bit later revealed that Hudson was locked down and being migrated to new java.net infrastructure.
I and the whole community was quite surprised by this, as we are supposed to be “notified as soon as we assign a date for [our] projects to move.” But by the time the developer community noticed, the project was already locked down, repository is read-only, and mailing lists can stop functioning any time. My immediate action was to contact the folks who are doing migration to get Hudson out of this cycle of the migration, but I was told that the ship has sailed and it was too late.
Even worse, there’s no ETA â€” it’ll definitely take a week, but since this is a Thanksgiving weekend, it can take longer, Oracle said.
I find this situation plain unacceptable, and e-mails from the earlier migration effort made me doubt if the new infrastructure is any better. I also had a pleasure of working closely with CollabNet folks over the past years and I was also involved in some earlier conversation and experiments about the new java.net infrastructure, and when it comes to performance and monitoring, CollabNet folks really knew what they are doing. So I had multiple reasons to worry if the new infrastructure can handle the load of java.net, which the old CollabNet-hosted one couldn’t handle.
But fortunately, since the general java.net migration has been announced, we’ve discussed the migration of some of the project infrastructure. So we’ve accelerated the plan and implemented it, so as not to lose the critical project infrastructure services.
Hudson mailing lists are moved to Google Groups. See more details here and here. The new mailing lists provide a real search capability, decent UI for archives, and it makes it easier for people with multiple e-mail addresses to post from multiple addresses and receive just one copy. The stability of the service is also much better.
Hudson core source code has been long synced to GitHub. We’ve been getting several contributions through that already, and people have been asking for Git migration for long time anyway. So going forward I’ll be committing to and producing releases from the Hudson repository on GitHub at https://firstname.lastname@example.org/hudson/hudson.git.
The new Git-based repository would be far snappier to work with, and it’ll make it easier for people to maintain private changes and contribute changes back. There’s also a work in progress to set up Gerrit to streamline the patch review process to the core. So I think this further reduces the barrier of entry to the Hudson project and accelerate the progress.
The migration of Hudson plugin repositories still needs to be discussed, so stay tuned for the updates in the dev list today or tomorrow. I’ve developed a bulk import program whose output can be seen here, so I’m going to propose this as the migration strategy.
My apologies that these changes had to happen quickly â€” I’m just as frustrated as you are, but given the circumstances, I think this is the best course of action. Hopefully everything will be in place within a few days. And in the mean time, thanks for your patience.