After reviewing diffs for Jetty and our 5.4...5.8 non-stop regression
whack-a-mole, I suggest we do NOT try to include Jetty 9.4.27 into LTS.
Instead of that, I started a 5.4.1 backporting branch where I included only
fixes unrelated to Jetty.
So...
- LTS:
- https://github.com/jenkinsci/winstone/pull/96
- Core PR is coming soom
- Weekly:
- https://github.com/jenkinsci/winstone/releases/tag/winstone-5.9
- https://github.com/jenkinsci/jenkins/pull/4542
On Thursday, March 5, 2020 at 9:33:53 AM UTC+1, Oleg Nenashev wrote:
>
> So, 2.204.4 was shipped on Tuesday. But it looks like our hurdles with
> 2.204.x are not over yet.
> Due to the Winstone upgrade in 2.204.3 (see my warning about that in the
> JENKINS-57888
> backporting comment
> <https://issues.jenkins-ci.org/browse/JENKINS-57888?focusedCommentId=383811&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-383811>)
>
> the release is also affected by JENKINS-60409
> <https://issues.jenkins-ci.org/browse/JENKINS-60409> and JENKINS-60199
> <https://issues.jenkins-ci.org/browse/JENKINS-60199>. Both these issues
> trace back to the Jetty regressions in 9.4.24 and Jenkins 2.205. The fixes
> have been released today in Winstone 5.9
> <https://github.com/jenkinsci/winstone/releases/tag/winstone-5.9>, but
> yet again the fixes involve Jetty upgrade. It is like a vicious cycle, and
> it looks like we need to backport the fixes to both 2.204.x and 2.222.x
> baselines.
>
> I suggest we organize a formal retrospective next week to discuss how we
> could handle such situations better in the Jenkins release process. I feel
> we could improve our weekly integration and LTS backporting process to
> prevent such issues in the future.
>
> Best regards,
> Oleg
>
>
> On Tuesday, March 3, 2020 at 10:39:19 AM UTC+1, Oleg Nenashev wrote:
>>
>> I sent a message yesterday, but I have not got a response so far. The
>> release have not been shipped yet.
>> Please stay patient (and keep sending good thoughts to the CDF operations
>> team and Linux Foundation legal team which work on resolving the code
>> signing certificate issues).
>>
>> Best regards,
>> Oleg
>>
>> On Monday, March 2, 2020 at 6:35:01 PM UTC+1, Mark Waite wrote:
>>>
>>> Agreed that we need 2.204.4
>>>
>>> On Mon, Mar 2, 2020 at 3:21 AM Oleg Nenashev <[email protected]> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We hit a regression in 2.204.3 due to the
>>>> https://issues.jenkins-ci.org/browse/JENKINS-60857 patch which we
>>>> missed.
>>>> The fix was not marked as LTS candidate, and hence it was missed during
>>>> the backporting process.
>>>>
>>>> I submitted https://github.com/jenkinsci/jenkins/pull/4539 with a fix.
>>>> Taking the community rating, IMO we need an out-of-order LTS release
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>> On Monday, February 17, 2020 at 4:02:39 PM UTC+1, Mark Waite wrote:
>>>>>
>>>>> New RC has been built. Thanks Oliver!
>>>>>
>>>>> On Mon, Feb 17, 2020, 2:30 AM Oleg Nenashev <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> The first RC is out and available for testing:
>>>>>> https://groups.google.com/forum/#!topic/jenkinsci-dev/GbkLba9Mm-g
>>>>>> From what I see Mark has discovered a critical issue there, so we
>>>>>> will need new RC bits soon.
>>>>>> Building RC manually with JDK8 looks like the best workaround for now
>>>>>>
>>>>>> On Friday, February 14, 2020 at 7:22:46 PM UTC+1, Raul Arabaolaza
>>>>>> wrote:
>>>>>>>
>>>>>>> Thanks everybody!
>>>>>>>
>>>>>>> On Thursday, February 13, 2020 at 7:16:34 PM UTC+1, Raul Arabaolaza
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hello all,
>>>>>>>>
>>>>>>>> According to the calendar the 2.204.3 RC should be out yesterday
>>>>>>>> Wednesday 12th, but it seems is not yet and there are no new commits
>>>>>>>> in the
>>>>>>>> stable-2.204 branch since 16 days ago. Has it been delayed for some
>>>>>>>> reason?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Raul Arabaolaza Barquin
>>>>>>>> Staff Software Engineer
>>>>>>>>
>>>>>>>> CloudBees, Inc.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> P: +34-637340429
>>>>>>>> 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/4f2586de-9ce6-4093-aba9-e6db7c844bae%40googlegroups.com
>>>>>>
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/4f2586de-9ce6-4093-aba9-e6db7c844bae%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>> --
>>>> 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/31a4b637-0411-43b3-988d-253b0b945012%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/31a4b637-0411-43b3-988d-253b0b945012%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
--
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/e858c633-888b-49f2-af2c-3f181fdd9db2%40googlegroups.com.
