Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: core
-
Labels:None
-
Similar Issues:
Description
Changing minimal JDK requirement has huge impact for most users as both jenkins master and slave need to be upgraded. As JDK 7 will be EOL soon, it seems a better choice to me to directly move to Java 8
- users to discover this compatibility break will only have to upgrade one
- impact on jenkins development is far more exciting.
also see JENKINS-27623
Attachments
Issue Links
- depends on
-
JENKINS-25333 Jenkins 1.586 not starting up using Java8
-
- Resolved
-
-
JENKINS-28120 Jenkins core to require Java7
-
- Resolved
-
- is related to
-
JENKINS-20679 Define manifest header in the jpi file to capture minimum Java requirement
-
- Resolved
-
- relates to
-
JENKINS-42709 Unable to build Jenkins with Java 8 set as target version
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue depends on |
Link |
This issue depends on |
Link |
This issue depends on |
Link |
This issue depends on |
Labels | 2.0 |
Summary | Upgrade minimum require Java version from 6 to 8 | Upgrade minimum require Java version from 7 to 8 |
Labels | 2.0 |
Workflow | JNJira [ 161836 ] | JNJira + In-Review [ 180860 ] |
Link |
This issue is related to |
Assignee | Nicolas De Loof [ ndeloof ] | Baptiste Mathus [ batmat ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Priority | Minor [ 4 ] | Critical [ 2 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | Cette demande est liée à "PR-2802 (Lien Web)" [ 15823 ] |
Link |
This issue relates to |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Description |
Changing minimal JDK requirement has huge impact for most users as both jenkins master and slave need to be upgraded. As JDK 7 will be EOL soon, it seems a better choice to me to directly move to Java 8 * users to discover this compatibility break will only have to upgrade one * impact on jenkins development is far more exciting. also see |
Hi,-- I have updated Jenkins to the latest version () |
Description |
Hi,-- I have updated Jenkins to the latest version () |
Hi, I have updated Jenkins to the latest version ([Jenkins ver. 2.164.1|https://jenkins.io/]) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error: [04/02/19 09:29:28] [SSH] Starting sftp client. [04/02/19 09:29:28] [SSH] Copying latest slave.jar... [04/02/19 09:29:28] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:29:28] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:29:30 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jar at hudson.FilePath.copyTo(FilePath.java:2191) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) With SSH Slave plugin version 1.29 is throwing a different error: [04/02/19 09:33:42] [SSH] Starting sftp client. [04/02/19 09:33:42] [SSH] Copying latest remoting.jar... [04/02/19 09:33:42] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:33:42] [SSH] Starting agent process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar remoting.jar -workDir /var/jenkins Apr 02, 2019 9:33:43 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /var/jenkins/remoting as a remoting work directory Both error and output logs will be printed to /var/jenkins/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:33:45 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Slave JVM has not reported exit code. Is it still running? [04/02/19 09:33:50] Launch failed - cleaning up connection [04/02/19 09:33:50] [SSH] Connection closed. ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Any ideas? Thank you! |
Description |
Hi, I have updated Jenkins to the latest version ([Jenkins ver. 2.164.1|https://jenkins.io/]) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error: [04/02/19 09:29:28] [SSH] Starting sftp client. [04/02/19 09:29:28] [SSH] Copying latest slave.jar... [04/02/19 09:29:28] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:29:28] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:29:30 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jar at hudson.FilePath.copyTo(FilePath.java:2191) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) With SSH Slave plugin version 1.29 is throwing a different error: [04/02/19 09:33:42] [SSH] Starting sftp client. [04/02/19 09:33:42] [SSH] Copying latest remoting.jar... [04/02/19 09:33:42] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:33:42] [SSH] Starting agent process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar remoting.jar -workDir /var/jenkins Apr 02, 2019 9:33:43 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /var/jenkins/remoting as a remoting work directory Both error and output logs will be printed to /var/jenkins/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:33:45 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Slave JVM has not reported exit code. Is it still running? [04/02/19 09:33:50] Launch failed - cleaning up connection [04/02/19 09:33:50] [SSH] Connection closed. ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Any ideas? Thank you! |
Comment |
[ Hi, I have updated Jenkins to the latest version ([Jenkins ver. 2.164.1|https://jenkins.io/]) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error: [04/02/19 09:29:28] [SSH] Starting sftp client. [04/02/19 09:29:28] [SSH] Copying latest slave.jar... [04/02/19 09:29:28] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:29:28] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:29:30 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jar at hudson.FilePath.copyTo(FilePath.java:2191) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76) at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) With SSH Slave plugin version 1.29 is throwing a different error: [04/02/19 09:33:42] [SSH] Starting sftp client. [04/02/19 09:33:42] [SSH] Copying latest remoting.jar... [04/02/19 09:33:42] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [04/02/19 09:33:42] [SSH] Starting agent process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar remoting.jar -workDir /var/jenkins Apr 02, 2019 9:33:43 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /var/jenkins/remoting as a remoting work directory Both error and output logs will be printed to /var/jenkins/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.29 This is a Unix agent Evacuated stdout Starting Selenium nodes on automation-jenkins-node Apr 02, 2019 9:33:45 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Slave JVM has not reported exit code. Is it still running? [04/02/19 09:33:50] Launch failed - cleaning up connection [04/02/19 09:33:50] [SSH] Connection closed. ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Any ideas? Thank you! ] |
Description |
Changing minimal JDK requirement has huge impact for most users as both jenkins master and slave need to be upgraded. As JDK 7 will be EOL soon, it seems a better choice to me to directly move to Java 8 * users to discover this compatibility break will only have to upgrade one * impact on jenkins development is far more exciting. also see |