I've submitted a pull request to the Jenkins packaging repository with a proposal to include some recent fixes that have been delivered in weekly. I'd
https://github.com/jenkinsci/packaging/pull/304 Mark Waite On Friday, April 1, 2022 at 5:28:20 AM UTC-6 [email protected] wrote: > Hello everyone, > > new LTS RC is available at > https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.332.2-rc32035.c5b_8249b_4842/jenkins-war-2.332.2-rc32035.c5b_8249b_4842.war > > Kudos to Mark Waite for detecting the missed bump! > > On Fri, Apr 1, 2022 at 9:24 AM Ildefonso Montero <[email protected]> > wrote: > >> Backport PR: https://github.com/jenkinsci/jenkins/pull/6425 >> >> On Fri, Apr 1, 2022 at 9:18 AM Ildefonso Montero <[email protected]> >> wrote: >> >>> Seems I missed to backport this: >>> https://github.com/jenkinsci/jenkins/pull/6329 >>> >>> I will prepare a new RC with that commit included >>> >>> On Fri, Apr 1, 2022 at 6:56 AM Mark Waite <[email protected]> wrote: >>> >>>> On Wednesday, March 23, 2022 at 10:50:32 AM UTC-6 Ilde wrote: >>>> >>>>> Hello everyone, >>>>> >>>>> Latest LTS RC was made public and it is ready to be tested. Final >>>>> release is scheduled for 2021-04-06. >>>>> >>>>> Please, report your findings in this thread. >>>>> >>>>> >>>> I've been running the release candidate since shortly after it was >>>> delivered and have not found any significant issues. >>>> >>>> While preparing the changelog for 2.332.2, I realized that there is a >>>> mention of remoting 4.13 in the backporting commit >>>> https://github.com/jenkinsci/jenkins/pull/6401 but I don't see >>>> remoting 4.13 being included in the release candidate build. The "About" >>>> page shows that it includes remoting 4.12. >>>> >>>> What is the consequence if Jenkins 2.332.2 includes remoting 4.12 (as >>>> 2.332.1 did) rather than remoting 4.13? >>>> >>>> Websocket agent does not reconnect ( >>>> https://issues.jenkins.io/browse/JENKINS-66446) is the issue in the >>>> pull request that mentions remoting 4.13. I've not been testing websocket >>>> agents, so I don't think that I would see the issue in my environment. >>>> >>>> Mark Waite >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/aeff5e68-7c88-4de2-9956-d3fb0bc9bcdfn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/aeff5e68-7c88-4de2-9956-d3fb0bc9bcdfn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> -- >>> >>> Ildefonso Montero Pérez >>> Staff Software Engineer >>> >>> CloudBees, Inc >>> >>> >>> >>> E: [email protected] >>> >> >> >> -- >> >> Ildefonso Montero Pérez >> Staff Software Engineer >> >> CloudBees, Inc >> >> >> >> E: [email protected] >> > > > -- > > Ildefonso Montero Pérez > Staff Software Engineer > > CloudBees, Inc > > > > E: [email protected] > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4b1eba97-79b7-4df9-b644-48130cd4ac12n%40googlegroups.com.
