Bugzilla – Full Text Bug Listing
| Summary: | Should our current version of Hudson be upgraded in hopes is better? | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alvaro.sanchez-leon, contact, ed, greensopinion, gunnar, kim.moir, matthias.sohn, nicolas.bros, pwebster, sbouchet, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 367238, 368529 | ||
3.0.0 seems like it will have lots of new features and new bugs. Wait for at least 3.0.2. We need fixes not enhancements. I vote for 2.2.0 for now. +1 for updating to Hudson 2.2. The template feature is a huge benefit for managing multiple jobs with similar configurations. We have been running 2.2 internally for a while without any problems. I don't think 3.0 is at the stage, yet, where it can be deployed in a production environment. It would make sense to me though to deploy the "Eclipse" Hudson release at Eclipse as soon as it's released. +1 for Hudson 2.2, since it solves the SVN polling issues that prevents jobs from being triggered automatically: http://issues.hudson-ci.org/browse/HUDSON-8982 I wonder what the Hudson committers recommend. It seems that 2.2 should be used on production systems. However, can we also install 3.0 on the sandbox to gather early feedback? Reminder, now (early this week of Feb 27th) would be a good time to upgrade to 2.2. Indigo SR2 is done ... and in a week or two we will be nearing the end of Juno M6. With the transition to Jetty and Winston having examined our setup, I think a good course of action would be to schedule a major Hudson upgrade over the summer. Ok, Juno has shipped summer is here so that means it's time to upgrade Hudson. At this time I'd like to use the following schedule: on July 9th upgrade the Sandbox instance to 2.2.1 and if all goes well upgrade the 'master' instance on Monday July 30th. -M. I've updated the sandbox. However it appears that Hudson 2.2.1 is incompatible with the Gerrit-Trigger plugin we use(the plugins available via the Hudson update site appear to be just as broken). I've reached out to the dev team to see if they have any advice. -M. (In reply to comment #8) > I've updated the sandbox. However it appears that Hudson 2.2.1 is incompatible > with the Gerrit-Trigger plugin we use FWIW, we still do not fully understand the security implications of having Hudson fire off a build based on Gerrit input (or code?), so I am uncomfortable with that plugin being used today. See bug 375350 (In reply to comment #8) > I've updated the sandbox. However it appears that Hudson 2.2.1 is incompatible > with the Gerrit-Trigger plugin we use(the plugins available via the Hudson > update site appear to be just as broken). I've reached out to the dev team to > see if they have any advice. > > -M. It seems the upgrade has nuked the SCM and gerrit event configuration of our jobs using the gerrit trigger plugin. I tried to reconfigure and tried to retrigger jgit.gerrit job for change 6314 using https://hudson.eclipse.org/sandbox/gerrit_manual_trigger/ but this didn't start the jgit.gerrit job (it should have). I'll try again in the evening, maybe I configured something in the wrong way. Restarting the gerrit connection of sandbox hudson didn't fix the problem. We also lost the SCM, Gerrit and Maven configuration for all mylyn-*-gerrit jobs. I don't see an option to execute Maven 3 any longer. Did the Maven plug-in get lost during the update? Looks like there were some bad ownership permissions in the .hudson dir on the sandbox that prevented the included maven3 plugin from appearing. -M. JGit and EGit verification builds work again. I had to reconfigure all jobs and now they are working again :) I've just updated the main Hudson instance to 2.2.1. All of the plugins appeared correctly(once I fixed the permissions) and jobs seem to be running. I'll close this bug, and people can open new ones if something is borked. -M. |
On cross-project list, the webmaster asked > -- We're currently running Hudson 2.1.2... We should perhaps upgrade to > 2.2.0, or perhaps even use the 3.0.0 milestone that is available at > Eclipse... Any thoughts? So, I'm opening this bug to give my thoughts (and hopefully collect others opinions). What I mostly advise is to make no changes till 2/17 ... that is when the main build related activity will be done for Indigo SR2. And, just my personality, I think better to limp along with known problems and frequent restarts rather than try something new and risk even worse, unknown problems. Beyond that, it would be important or at least be interesting to see what is fixed/changed in 2.2.0 or 3.0.0 but I couldn't find any "what's new" summaries (from quickest search with DuckDuckGo). Anyone have any links? Any fixes related to NFS? any bugs match our "classnot found" exceptions? But, given my impression and experience with Hudson, it will be be just fine to move up to any 'ol release or build ... somethings will get better ... and somethings will get worse ... some of the most predictable software I have seen? :) [ha ha, really, just kidding ... I suspect there is steady improvement to those who look at overall picture involving all consumers ... and Eclipse is just "special" ... just wait till those powerPC's are hooked in ... we'll be extra special then :) ].