Use the latest version #2274
Use the latest version #2274
Conversation
In particular, this will install Java7 when build agents don't have any Java. 1.9 tries to install Java6 which is no good.
|
why install 1.7, whilst it is the minimum supported it is old, unpatched and very possibly filled with security holes. Given we are trying to be secure by default this seems like a backward step, and many people may not be java shops and aware of any issues. (yes we are not really running the salve as a "service" and exposing ports for attacks, but at the same time...) |
|
🐝 I think - but upgrading detached plugins seems a little screwy, its only for very old upgrades (running a version of jenkins prior to when the plugin was first detached) and an upgrade can (and should) be upgrading plugins - not sure why the upgrade wizard[1] doesn't resolve a newer version of the plugin if it is available from the UC... [1] does it exist yet? |
|
👎 This is irrelevant in Jenkins 2.x, as the setup will always install the newest release. And this plugin doesn't even qualify for the core detachment compatibility code, so it could be removed altogether. @tfennelly Or is there a reason this is still around? It never was part of core, therefore never detached, therefore will never be installed, right? |
oleg-nenashev
added
the
needs-more-reviews
|
seems it's not required anymore |
|
I'm fairly sure that this change will only effect the test harness. |
|
Filed JENKINS-34583. Closing this. |
In particular, this will install Java7 when build agents don't have any
Java. 1.9 tries to install Java6 which is no good.