Upgrading remoting to Java 8

[Oleg Nenashev]

Hi all,

A while a go I have created a ticket for upgrading Remoting to Java 8 (JENKINS-43985). I was waiting with this step, because 2.46.x LTS was Java 7 compatible. Now we have completely switched to Java 8 in 2.60.1, hence it is not a blocker anymore. So I would like to update the Java requirement in Remoting, especially since there is an interest to do it in order to use some Java 8 features (e.g. here).

Potential impact, edge cases:

• If somebody uses custom Remoting versions (e.g. by downloading the latest version to pick fixes), such approach will stop working on Java 7. So, all users of Java 7 will have to do custom builds if they want to get Remoting fixes
  
• Backporting of fixes (e.g. custom forks or security backports) may be complicated
• Swarm Plugin's Client will have to update to Java 8 in order to bundle the new remoting version
  

Does anybody have any concerns about it?

Thanks in advance,
Oleg Nenashev

[Mark Waite]

No concerns from me.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c784b3a4-c64d-413d-872c-4cad1d0c5642%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

> On 30. Jun 2017, at 15:05, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> Potential impact, edge cases:

What about graceful error handling of Java 7 instances, e.g. Maven plugin? IIRC from the 6-to-7 upgrade, the fallback mechanism to the lower JDK would be affected by this...?

Not that I care that much, Maven projects need to be burninated, but still -- if it's affected, we should at least be aware of it.

[Oleg Nenashev]

Hi,

AFAIK there is no graceful handling of errors in the Maven project plugin. There was just a workaround which reconfigures Java settings, but it does not guarantee that Jenkins master will actually work. In the plugin's Wiki it is explicitly said that versions 2.54+ should be launched with Java 8 only, so I do not consider it as a problem.

BR, Oleg

понедельник, 3 июля 2017 г., 0:18:30 UTC+2 пользователь Daniel Beck написал:

[Oleg Nenashev]

I will add it to the governance meeting agenda along with another topics I would like to discuss

понедельник, 3 июля 2017 г., 10:54:06 UTC+2 пользователь Oleg Nenashev написал:

[Jesse Glick]

It is a technical decision and there does not seem to be any pushback so I think you can just do it. No need to take up time during a governance meeting.

[Oleg Nenashev]

I need it for other topics anyway

2017-07-14 20:58 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>:

It is a technical decision and there does not seem to be any pushback so I think you can just do it. No need to take up time during a governance meeting.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/CDZaG3dr-kc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2wBbT63P_mOyeRo6Nc9qjUtkJjpkJ0bVbR8HW2DHRNjA%40mail.gmail.com.

[Daniel Beck]

> On 14. Jul 2017, at 20:58, Jesse Glick <jgl...@cloudbees.com> wrote:
>
> It is a technical decision

Right; does not seem to be a project governance issue.

[Oleg Nenashev]

Created https://github.com/jenkinsci/remoting/pull/184

пятница, 14 июля 2017 г., 21:55:12 UTC+2 пользователь Daniel Beck написал: