Hello, I seem to remember this was done in the past, but not anymore indeed. Could we push the RC binaries somewhere?
I'm asking because we have some jobs (one in particular) that is able to run many builds against a given Jenkins version. So, if it existed, we would be able to OOTB test many combinatorials using like "2.60.1-rc1". I guess that could be valuable for the community as regression testing. [In the meantime,] we could obviously upload the binaries by hand somewhere, but you know how it is :). Manual is things you do once or twice :). Any rationale why we wouldn't reconsider pushing those? (Note: we need it to be under the typical Maven coordinates, just different version, so that it works. It's basically using -Djenkins.version=the-version). I guess this question is mainly for Oliver who's doing the heavy lifting, but generally @all WDYT? Thanks a lot! ---------- Forwarded message ---------- From: Mark Waite <[email protected]> Date: 2017-06-09 15:17 GMT+02:00 Subject: Re: Jenkins 2.60.1 LTS RC testing started To: [email protected] I'll try to spend time on it today to create a duplication environment outside of my home network. I don't expect it to be difficult to duplicate, but I can provide that environment. It will be a good test for me to assure that I've understood the details that contribute to the problem. I won't likely be able to start on it until after work today. Earliest results probably won't be available until tomorrow morning. Mark Waite On Fri, Jun 9, 2017 at 12:43 AM Oliver Gondža <[email protected]> wrote: > On 2017-06-09 06:41, Mark Waite wrote: > > I confirmed that the 2.46.3 with latest plugins for that release is able > > to connect to all those machines. > > Can you point us to a way to reproduce this? It indeed seems related to > 7dbcd02cf71eabf92e58522968230d564d9b99e5, the only backported change. > > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/c404fcea-3ad9-0343-c1b0-af87aeadc967%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/ msgid/jenkinsci-dev/CAO49JtEZT2GhUEcQsoy0d3Kkap0f7 MnYWz1FP0E2a_aYJByfJA%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEZT2GhUEcQsoy0d3Kkap0f7MnYWz1FP0E2a_aYJByfJA%40mail.gmail.com?utm_medium=email&utm_source=footer> . 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS59LCVcoacQyfLQdFsSWjiQCUAv9FYMLBkWYCW4uNgeyQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
