4.) get rid of Java6 support? It is EOL anyway...
LieGrue, Strub > Am 05.04.2017 um 19:09 schrieb John D. Ament <[email protected]>: > > Hey guys > > So I had a bit of a back and forth with Gav this morning, RE our builds and > the sudden failures. One of the changes in a recent jenkins release made > it so that remoting features require java 7. You can see their notes here: > https://github.com/jenkinsci/remoting/blob/master/docs/remoting-3-compatibility.md > > Because of this, there's only a few options we have. > > 1. Convert existing builds from maven projects into freestyle projects. > Implement a maven step. > > 2. Don't use remoting. > > 3. Switch to Jenkinsfile syntax. > > Not using remoting would mean some changes in our build structures, which > are really not long term. Converting gives us limited benefit. I'd like > to go with #3 because of this issue, to give us the broadest range of > support. I'm going to start with the minimal list that Mark put together > as jobs to convert. We can add more as we see fit. Once I have a pipeline > running, I'll check in that file and point to it. > > John
