| Summary: | Update Hudson | ||
|---|---|---|---|
| Product: | Community | Reporter: | Eclipse Webmaster <webmaster> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, kim.moir |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Eclipse Webmaster
Privilege escalation? What kind of escalation? Sounds fine by me. I read some advice recently about upgrading databases ... don't just schedule the time to do the upgrade ... also schedule time to do the rollback ... just in case, needed. I thought that was funny ... and good advise! So, as long as we can rollback if needed (and, I know we can). Thanks for taking care of our build machines. > I'd like to do the update Monday the 24th at 12pm.
There's a new kernel available -- can we update/reboot build.eclipse.org at the same time?
It's ok with me. -M. Will the slaves be rebooted at the same time? If not, could you please reboot the mac slave. It's unhappy today. Sure thing. -M. Ok, I've updated and restarted build, installed Hudson 1.389 and restarted the master and all slaves. I'm also taking this opportunity to install the build timeout plugin(bug 319909) so Hudson will restart when all running jobs have finished and that should be it for a while. Please let me know if there are any problems. -M. Closing. -M. |