|[cross-project-issues-dev] Hudson status.|
Hi Folks,We've had some issues with our Hudson setup, and while things have been better post Helios it's still not at the same level as other Eclipse.org services. As such we're working on a new Hudson deployment in order to address the stability issues we've had with our master instance, and continue to have on our slave(s).
What does this mean to you? Next week we're going to work on getting the slaves connected, and that means the current slave(build2) will be disconnected next Wednesday(August 11). All you should need to do to prepare is to 'move' your jobs back to the current master instance by unticking the 'Tie this project to a node' option in your job config.
Once we've made a formal announcement, you'll be able to get jobs moved by filing a bug(against Hudson) requesting the move. Webmaster will then copy your job from the old to the new and you should be off and running. Now you may need to tweak your job configurations a bit(make sure you're using the correct JVM and so on) but it should 'just work'.
You can find a little more documentation here: http://wiki.eclipse.org/Hudson .
If you have any specific questions please let me know. -Matt. -- Eclipse WebMaster - webmaster@xxxxxxxxxxx Eclipse Summit Europe, Nov 2-4 . Visit http://www.eclipsecon.org/summiteurope2010/ Questions? Consult the WebMaster FAQ at http://wiki.eclipse.org/index.php/Webmaster_FAQ View my status at http://wiki.eclipse.org/index.php/WebMaster
Back to the top