[Geoserver-devel] Jenkins on Ares

Hello all,

I need to install a few Jenkins plugins on Ares, but they require a newer version of Jenkins than that which is currently installed. So I have a few questions to ask:

  1. One of the plugins requires Jenkins 1.612. We are currently at 1.558 on Ares, which was from April 2014. Is it possible that any of the Jenkins jobs configured on Ares be affected by upgrading?

  2. Is there a particular version of Jenkins that we may prefer to upgrade to, rather than 1.612? This version is from May 2015.

  3. If everyone is okay with upgrading, when can the upgrade be done and what time of day? I realize that Ares is used throughout all different time zones, so I would like to minimize disruptions to work being done by the community.

Any questions or concerns, please feel free to contact me.

Regards,
Chris

···

Christian Del Pino

DevOps Engineer

Boundless | www.boundlessgeo.com
Email: cdelpino@anonymised.com

On 29/07/16 08:41, Christian Del Pino wrote:

1. One of the plugins requires Jenkins 1.612. We are currently at 1.558 on
Ares, which was from April 2014. Is it possible that any of the Jenkins
jobs configured on Ares be affected by upgrading?

This is always possible, but in my view it is better to upgrade and fix problems. I think we should try to use a more up-to-date version so we can benefit from security fixes.

2. Is there a particular version of Jenkins that we may prefer to upgrade
to, rather than 1.612? This version is from May 2015.

If we are only upgrading every two years, would you recommend that we switch to using the stable/LTS build (currently 2.7.1)? Blog post on Jenkins 2:

"This release also officially marks the end-of-life for Jenkins 1.x. There won’t be any future release of Jenkins 1.x beyond this point. If you are worried about the upgrade, don’t be! The core of Jenkins is still the same, and all the plugins & existing configuration will just work."
https://jenkins.io/blog/2016/07/07/jenkins-2/

3. If everyone is okay with upgrading, when can the upgrade be done and
what time of day? I realize that Ares is used throughout all different time
zones, so I would like to minimize disruptions to work being done by the
community.

You will always inconvenience someone so I suggest some time when it is the weekend or at least after business hours in BC Canada and Italy to minimise disruption, as that is where many developers are. In any case, we can live without Jenkins for a day.

Much more important in my view is to avoid release time. This usually happens on the week after the 18th of the month. Note that the GeoTools 15.1 / GeoServer 2.9.1 releases are delayed and are imminent. Releases are performed using Jira automation so it is crucial the the Jira upgrade is delayed until after Devon and Jody have completed these releases.

Thanks again, Chris, for your efforts and Boundless' generosity in providing this service.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

Thanks for the quick response Ben. Responses below inline:

···

On Thu, Jul 28, 2016 at 5:47 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

On 29/07/16 08:41, Christian Del Pino wrote:

  1. One of the plugins requires Jenkins 1.612. We are currently at 1.558 on
    Ares, which was from April 2014. Is it possible that any of the Jenkins
    jobs configured on Ares be affected by upgrading?

This is always possible, but in my view it is better to upgrade and fix problems. I think we should try to use a more up-to-date version so we can benefit from security fixes.

I agree that we should be more up to date. Hopefully no problems are encountered after upgrading or if there are any, that they are minimal.

  1. Is there a particular version of Jenkins that we may prefer to upgrade
    to, rather than 1.612? This version is from May 2015.

If we are only upgrading every two years, would you recommend that we switch to using the stable/LTS build (currently 2.7.1)? Blog post on Jenkins 2:

“This release also officially marks the end-of-life for Jenkins 1.x. There won’t be any future release of Jenkins 1.x beyond this point. If you are worried about the upgrade, don’t be! The core of Jenkins is still the same, and all the plugins & existing configuration will just work.”
https://jenkins.io/blog/2016/07/07/jenkins-2/

I’d like to upgrade more frequently throughout the year rather than every two years, if that is okay with the community. As far as versions, I can look into upgrading to the latest stable release, assuming everyone is in agreement with the version to upgrade to.

  1. If everyone is okay with upgrading, when can the upgrade be done and
    what time of day? I realize that Ares is used throughout all different time
    zones, so I would like to minimize disruptions to work being done by the
    community.

You will always inconvenience someone so I suggest some time when it is the weekend or at least after business hours in BC Canada and Italy to minimise disruption, as that is where many developers are. In any case, we can live without Jenkins for a day.

Much more important in my view is to avoid release time. This usually happens on the week after the 18th of the month. Note that the GeoTools 15.1 / GeoServer 2.9.1 releases are delayed and are imminent. Releases are performed using Jira automation so it is crucial the the Jira upgrade is delayed until after Devon and Jody have completed these releases.

The weekends work for me to get this done. If the community would like to give me dates and times that are available for me to do this, that would help out.

Thanks again, Chris, for your efforts and Boundless’ generosity in providing this service.

No problem. It’s my please to help out with this.

Regards,
Chris

Kind regards,


Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

Christian Del Pino

DevOps Engineer

Boundless | www.boundlessgeo.com
Email: cdelpino@anonymised.com