My Jenkins current version is 2.19.3 with Java 7, and I am planning to upgrade my NXRM to 3.18 which will use JAVA 8, so does my Nexus upgrade impact Jenkins and Sonar running on Java 7?
Jenkins and Sonar work with java8 with no problems.
Every one of the apps you list starts up its own jvm; they are all independent. As long as you launch the right jvm you are fine. It worries me that as a developer, you'd be asking this.
Since 2.60, Jenkins has required Java 8 jvm to run. As Jenkins 2.164, it supports running on Java 11 jvm.
Since SonarQube, LTS 6.x, I believe, it has required Java 8 jvm to run. As of LTS 7.9, Java 11 jvm is required. It will still anaylze java 8 code.
Evidently, you should really be upgrading your SonarQube and especially Jenkins instances well. Jenkins in particular has had many security improvements.
Related
I have a basic question, I am trying to install jenkins on AWS EC2 ubantu instance.
I see Jenkins requires Java 11 to use newer versions - https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/
I am planning to run junit tests which supports Java 8 on Jeknins node.
If I install Jenkins with Java 11 on EC2, does it impacts executing junits tests?
UPDATED:
Why Install automatically doesn't show list of options to select jdk versions?
I was seeing notification in Jenkins regarding upgrading the Java version from 8 to 11 for future Jenkins release support. But I am not seeing that notification now. So little confused whether Jenkins continuing support with Java 1.8?I was getting the java support notification to stop
From the Jenkins documentation.
Java 8 or Java 11 are required for running modern versions of Jenkins.
Upgrading an existing Jenkins setup from Java 8 to Java 11? See the
upgrade guidelines.
Java 11 Docker installation instructions are included in "Downloading
and running Jenkins in Docker"
Starting with the Jenkins 2.357 weekly release, Java 11 or Java 17
will be required. Java 8 is supported on the Long Term Support release
line until the September 2022 LTS release.
Java 17 users can run the jenkins/jenkins:jdk17 Docker image.
All other Java versions are not supported.
These requirements apply to all components of the Jenkins system,
including Jenkins controller, all types of agents, CLI clients, and
other components.
Jenkins project performs a full test flow with the following JDK/JREs:
OpenJDK JDK / JRE 11 - 64 bits
OpenJDK JDK / JRE 17 - 64 bits
JRE/JDKs from other vendors are supported and may be used. See our
Issue tracker for known Java compatibility issues.
The comment by Mark Rotteveel is very important: running Jenkins with Java 11 is not a big deal, the problem is what you can build. The biggest limitation is with Maven Jobs: if you have Maven projects based on Java 8 and you use Jenkins' Maven Job for them, you'll have to change something.
See https://plugins.jenkins.io/maven-plugin/ where it says:
Jenkins >= 1.520 requires Java 6 thus Maven jobs must be launched with Java >= 6.
Jenkins >= 1.612 requires Java 7 thus Maven jobs must be launched with Java >= 7.
Jenkins >= 2.54 requires Java 8 thus Maven jobs must be launched with Java >= 8.
Jenkins >= 2.357 requires Java 11 thus Maven jobs must be launched with Java >= 11.
The same thing is said at https://community.jenkins.io/t/maven-builds-fails-after-upgrade/3850/2.
Note that the migration guide at https://www.jenkins.io/doc/upgrade-guide/2.361/ does not make evident this limitation: it says you can still use Java 8 to build your projects but it does not say that you cannot build them as Maven Jobs anymore.
Similarly this post says:
The controller and agent must run java 11. [...] Your jobs however can
run whatever they want.
But, again, this is true only if you opt out of Maven Jobs.
I was working on jenkins and working fine but i don't know what happened Jenkins shows following errors and no jobs are visible to me after that:
I am new in jenkins please help me to solve this.
As I understand the problem it could happened in cause of downgrading jenkins version or updating plugins "Pipeline: Node and Processes".
You need to restore previous jenkins version or downgrade plugin.
Additionally you can configure jenkins to get plugins' versions which fit your jenkins version in "Manage Jenkins" -> "Manage plugins" -> "Advanced" -> "Update site" and set the version you are currently using (for example https://updates.jenkins.io/stable-2.176/update-center.json)
Jenkins plugins are dependent on Jenkins LTS versions in use. Best way is while installing the Jenkins take latest (but stable) version of plugins.
Since you are using 1.176 version and trying to upgrade the plugins, the latest plugins do not support the older version of Jenkins (since Jenkins follow Parallel incremental development).
You can resolve the problem in 2 ways.
1. Downgrade the plugins and keep the LTS Jenkins version as it is. (not preferred solution since you will not be able to use latest functionality of the plugins and using old plugins is not secured).
Downgrade of plugins will also be suggested by Manage Jenkins --> Manage Plugins --> Installed
2. Upgrade Jenkins version (LTS 2.24x.x)
It is time taking option, but if you are heavely using jenkins for your work it is more suggested to upgrade the version. Besides new plugins have more secured and vast functionalities.
You can check the Changelog and can decided which version is good for you.
Take a reference of Upgrading Jenkins link.
To understand plugins and Jenkins LTS version dependency, use Jenkins wiki(Confluence Page).
e.g. Pipeline:Node and Processes plugin wiki indicates that for version 2.29 you need to have Jenkins version 1.150.1 or higher.
Note: Latest Jenkins version supports HTTPS instead of HTTP URL for advanced proxy options under Manager Jenkins.
I am trying to use jekins for deployment of my patch so here the server on which I want to deploy is a Windows server and my Jenkins is a Aix system and also my Jenkins version is 2.9 and it's run on java 7 where as the application I am deploying has a constraint that it could only be run on java 6 which is on Windows hence I need a solution for this java 7 to to java 6 slave connection.
I have resolved this issue by just installing a java 7 on the windows server with the constraint,
but the java 7 isn't configured in the path variable i have kept a command handy with the complete path of bin directory of the java 7 installed on the windows so i can connect via slave.jar to my jenkins server giving the path and executing the slave.jar with java 7 so that i dont get a major minor version error, and later on since its not in the path further use java 6 for later processing of windows server.
I want to configure IOS project jobs in linux jenkins. Is it possible to configure IOS jobs in Linux Jenkins, without OSX PC.
You need to have a OSX machine running. It's a matter of licensing (same problem appears for Visual Studio). But there is an XCode Plugin to help you with it Jenkins Xcode Plugin.
edit:
there are several tutorials out there on how to give jenkins an iOS-build slave (check out one).