Upload RC binaries in a maven repo somewhere? (was: Fwd: Jenkins 2.60.1 LTS RC testing started)

[Baptiste Mathus]

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 <mark.ea...@gmail.com>
Date: 2017-06-09 15:17 GMT+02:00
Subject: Re: Jenkins 2.60.1 LTS RC testing started
To: jenkin...@googlegroups.com

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 <ogo...@gmail.com> 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 jenkinsci-dev+unsubscribe@googlegroups.com.
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 jenkinsci-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEZT2GhUEcQsoy0d3Kkap0f7MnYWz1FP0E2a_aYJByfJA%40mail.gmail.com.

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

[Daniel Beck]

> On 9. Jun 2017, at 15:27, Baptiste Mathus <m...@batmat.net> wrote:
>
> but not anymore indeed

Isn't this what you're asking for?

> Thu Jun 08 07:08:17 UTC 2017 [olivergondza/…] [CREATED] snapshots/org/jenkins-ci/main/jenkins-core/2.60.1-SNAPSHOT/

[Jesse Glick]

On Fri, Jun 9, 2017 at 9:54 AM, Daniel Beck <m...@beckweb.net> wrote:
> Isn't this what you're asking for?
>
>> Thu Jun 08 07:08:17 UTC 2017 [olivergondza/…] [CREATED] snapshots/org/jenkins-ci/main/jenkins-core/2.60.1-SNAPSHOT/

https://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/2.60.1-SNAPSHOT/

I guess you mean?

Would be more comfortable to have actual release versions. OTOH I seem
to (vaguely) recall some problem in the past with these being mistaken
by some piece of code for actual releases and offered to users.

[Daniel Beck]

> On 9. Jun 2017, at 15:56, Jesse Glick <jgl...@cloudbees.com> wrote:
>
> OTOH I seem
> to (vaguely) recall some problem in the past with these being mistaken
> by some piece of code for actual releases and offered to users.

This happened with the 2.0 betas IIRC, and before then, with versions like 1.509.2.JENKINS-14362-jzlib (not sure whether that specific one, but builds for specific issues were involved).

[Stephen Connolly]

Periodic reminder that staging feature of the other maven repository server would be awesome here if we switched to that and asked for a oss license for the pro features.

Would also be useful for some jenkinsci-cert activities

--
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/7172B6AC-97D8-4580-8247-0D1CB5C597CB%40beckweb.net.

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

--

Sent from my phone

[Baptiste Mathus]

So indeed I had overlooked the snapshot. Issue is, I tested this on Friday and this doesn't work, because our maven repo manager main group repo isn't configured to access the Jenkins snapshots one.

So though this can be fixed, this is not an total ootb option I was hoping for :). I'll work with my colleagues to see the options to make this possible.

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-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7172B6AC-97D8-4580-8247-0D1CB5C597CB%40beckweb.net.

[Stephen Connolly]

On Sun 11 Jun 2017 at 20:58, Baptiste Mathus <m...@batmat.net> wrote:

So indeed I had overlooked the snapshot. Issue is, I tested this on Friday and this doesn't work, because our maven repo manager main group repo isn't configured to access the Jenkins snapshots one.

So though this can be fixed, this is not an total ootb option I was hoping for :). I'll work with my colleagues to see the options to make this possible.

I or James can add the snapshots repo as a source for our internal proxy. I'm surprised Jesse didn't ask for it already!

Thanks!

Le 9 juin 2017 4:02 PM, "Daniel Beck" <m...@beckweb.net> a écrit :

> On 9. Jun 2017, at 15:56, Jesse Glick <jgl...@cloudbees.com> wrote:
>
> OTOH I seem
> to (vaguely) recall some problem in the past with these being mistaken
> by some piece of code for actual releases and offered to users.

This happened with the 2.0 betas IIRC, and before then, with versions like 1.509.2.JENKINS-14362-jzlib (not sure whether that specific one, but builds for specific issues were involved).

--
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/7172B6AC-97D8-4580-8247-0D1CB5C597CB%40beckweb.net.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6AGXW9MpRC49nTLMZ52QZZqPP0nJLtaqhHU4i%2BrmAhdQ%40mail.gmail.com.

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