Thanks for the comments everyone. There looks like there is strong consensus, so I'll start the official [VOTE] thread. Please make your informal +1's here official by replying to that thread.
WRT Jenkins/Pipeline, I will comment on their open issue: https://issues.jenkins.io/browse/JENKINS-53372 (related issue https://issues.jenkins.io/browse/JENKINS-63047). It already links to the slightly pessimistic EOL tracker here: https://endoflife.date/apache-groovy (which already has 2.4 as effectively EOL). Paul. On Sat, Jun 29, 2024 at 10:57 PM Christopher Smith <chry...@gmail.com> wrote: > > That's the one. Agreed that I don't think there is likely to be any > showstopper, since Pipeline doesn't use any esoteric syntax, but somebody has > to do it, and we should at least alert the Jenkins people before we EOL a > core component of a major CI tool. > > > On Sat, Jun 29, 2024, 06:14 Jochen Theodorou <blackd...@gmx.org> wrote: >> >> On 28.06.24 18:35, Christopher Smith wrote: >> > Heads up that Jenkins (as of plugin parent 4.83, and at least >> > workflow-cps is still on 4.80) still uses Groovy 2.4.21. The CPS plugin >> > is a drastic ASTT, and it's core to modern Jenkins pipelines. >> >> you mean this I think: >> https://github.com/jenkinsci/workflow-cps-plugin/tree/master/lib/src/main/java/com/cloudbees/groovy/cps >> >> That is indeed a handful, but I don't think that is really a stopper. >> The problem is probably finding somebody brave enough to start it. >> >> bye Jochen >>
