Hi, Guys.
I’m considering the following combination of configurations. I wanna confirm the compatibility of each version with the plugin, supporting or not.
I investigated regarding this, however I couldn’t find any info. If anyone knows the following would you please reply in here. Thank you.
-Jenkins and Ansible
In the following URL , as my understanding, there is the result of the support/verification track record for Jenkins with "2.440.3"and Ansible (LTS version) with only “2.15.12”, “2.16.7”, “2.17.0”, is this correct?
The latest Jenkins version(“2.254.X”) has no support/verification record, correct?
-Jenkins and Gitlab
In the following URL , as my understanding, there is the result of the support/verification track record for Jenkins with “2.426.3” and Gitlab with only “1.8.1”, is this correct?
Do you know is there compatibility between Gitlab “1.17.1” and Jenkins version(“2.440.X”, “2.452.X”)?
Unfortunately, you’re misunderstanding the information on that page. There is no concept of a “support / verification track” for Jenkins plugins The plugin version information page shows the distribution of plugin installation versions on Jenkins versions. That shows which Jenkins versions are running which versions of the plugin.
The plugin health score page shows the overall health of the plugin based on several measurements.
Jenkins 2.440.3 is the minimum required version of Jenkins controller that is supported with the most recent release of that plugin. That is not the only version where the plugin has been used.
You are welcome to test older plugin versions with Jenkins versions but that is taking all the validation responsibility yourself, rather than using the plugin version information to see which Jenkins versions are being used with which plugin versions.
The Jenkins project security team only provides security fixes for the most recent weekly release and the most recent LTS release. Choosing to run an older version like Jenkins 2.426.3 means that you’re accepting running a version with known security vulnerabilities. Most organizations don’t want to run versions with known security vulnerabilities.