Upgrading remoting to Java 8

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

--
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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

Mark Waite-2

No concerns from me.


On Fri, Jun 30, 2017, 7:05 AM Oleg Nenashev <[hidden email]> wrote:
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

--
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 [hidden email].
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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH%3DNRz%3DgpjSCYUS7Zg8EwvrraSXpWhbpGkJxzeY8D%2B5Kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

Daniel Beck
In reply to this post by Oleg Nenashev

> On 30. Jun 2017, at 15:05, Oleg Nenashev <[hidden email]> 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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5BF34593-EED4-48EC-8785-D61B1A4690DA%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

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 написал:

> On 30. Jun 2017, at 15:05, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZBKmUocKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> 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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3aca58f6-4ce4-403b-965d-42d99b665a15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

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 написал:
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 <a href="https://wiki.jenkins.io/display/JENKINS/Maven+Project+Plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaven%2BProject%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0mkr2BeQmafObgWj9i2Y7vmAYg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaven%2BProject%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0mkr2BeQmafObgWj9i2Y7vmAYg&#39;;return true;">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 написал:

> On 30. Jun 2017, at 15:05, Oleg Nenashev <[hidden email]> 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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9d754f18-bd2c-4d67-a83b-204ce1f11a4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

Jesse Glick-4
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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2wBbT63P_mOyeRo6Nc9qjUtkJjpkJ0bVbR8HW2DHRNjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

Oleg Nenashev
I need it for other topics anyway

2017-07-14 20:58 GMT+02:00 Jesse Glick <[hidden email]>:
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2wBbT63P_mOyeRo6Nc9qjUtkJjpkJ0bVbR8HW2DHRNjA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBEWy%3D1-vKAxgEU3ocyT9PF7ue1j3qNi%3DOhKmdm2xm2KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

Daniel Beck
In reply to this post by Jesse Glick-4

> On 14. Jul 2017, at 20:58, Jesse Glick <[hidden email]> wrote:
>
> It is a technical decision

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/77C38DF6-AF21-4EBF-B864-27649ECC9075%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Upgrading remoting to Java 8

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

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

> On 14. Jul 2017, at 20:58, Jesse Glick <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="YqG4blalAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jgl...@...> wrote:
>
> It is a technical decision

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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0f2706e6-ef1c-43f2-8c54-09fc1a7e6253%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...