Backporting for LTS 2.164.3 started

[Oliver Gondža]

Backporting has started and the RC is scheduled for 2019-04-24.

Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
Fixed:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-fixed
Rejected:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-rejected
--
oliver

[Baptiste Mathus]

Just added lts-candidate on https://issues.jenkins-ci.org/browse/JENKINS-56403 merged yesterday. 

I think it could be considered given the regression fix PR is fairly small and has had dedicated tests added: https://github.com/jenkinsci/jenkins/pull/3925

Do you think it would be eligible to backporting in upcoming .3?

Thanks

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/845a8da6-c20e-1f50-e69e-319fe283b1f7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Oliver Gondža]

Baptiste, thanks for the suggestion but I lean towards skipping this for
2.164.3.

To the best of my understanding, this issues was present for 6 entire
LTS lines (possibly without being reported). Given the consequences are
duplication of a renamed agent after restart, I dare to dispute this is
a blocker issue to begin with.

Or do I miss something?

On 19/04/2019 09.53, Baptiste Mathus wrote:
> Just added lts-candidate on
> https://issues.jenkins-ci.org/browse/JENKINS-56403 merged yesterday.
> I think it could be considered given the regression fix PR is fairly
> small and has had dedicated tests added:
> https://github.com/jenkinsci/jenkins/pull/3925
>
> Do you think it would be eligible to backporting in upcoming .3?
>
> Thanks
>
> Le lun. 15 avr. 2019 à 11:54, Oliver Gondža <ogo...@gmail.com

> <mailto:ogo...@gmail.com>> a écrit :

>
> Backporting has started and the RC is scheduled for 2019-04-24.
>
> Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
> Fixed:
> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-fixed
> Rejected:
> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-rejected
> --
> oliver
>
> --
> 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 jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/845a8da6-c20e-1f50-e69e-319fe283b1f7%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

> --
> 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 jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-de...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5kQG7s-Ex1PQhO%3DUYxC_Hb3fNXtKGjhgrC6k%3Df8afOVA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5kQG7s-Ex1PQhO%3DUYxC_Hb3fNXtKGjhgrC6k%3Df8afOVA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

--
oliver

[Baptiste Mathus]

I agree with the rationale. I do not think users renaming agents is that common, and yes, it is said to have been introduced in Jenkins 2.8, so it would have exploded earlier if this was that problematic.

Thanks for considering this request in any case.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2deacef6-a160-936a-3b41-d523f97f2fa2%40gmail.com.