Hi,
This sounds good to me.
I wonder if we should have the testing sandboxes use the same version of Jenkins though? If it doesn't we could have deployment failures due to using features from the new version.
Thanks,
James
On Tue, 5 Jul 2011 16:39:26 +0300, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
I'd like to upgrade Jenkins on the production to be close to sandboxes (which always use latest) and local development to be performed per this milestone's blueprints. android-build.linaro.org runs 1.400, latest is 1.418. Interim versions were tested regularly on sandboxes, and I reviewed changelog and saw no backwards-incompatible changes which might affect us. Actually, it has few nice fixes and features useful for us, including those which raised discontent with using Jenkins for our usage patterns:
- Label expression logic wasn't supporting a binary operator sequence
like "a || b || c" (issue 8537)
- Move Jenkins URL setting from E-mail Notification to its own section
in the main configuration.
- Added an extension point to allow prodding the NodeProvisioner into
taking action faster than it might usually.
- When there are absolutely no executors for a specific label, there was
an unnecessary delay in provisioning the first node for that label.
- Added a new build parameter type that shows a text area
So, I'd propose to perform upgrade European morning on Thursday, 7th.
Please let me know if there're any concerns.
-- Best Regards, Paul