Re: 1.509.4 backporting

Hi, For issue JENKINS-9637 two more commits should be backported: dd2b4a180582e4e8e6bdd8a511a457d201fce1ed and f9b9c192498ef85126ab41a0af8323cddd2c682c where the second one is only the changelog entry. Regards, Stefan Am Donnerstag, 19. Septem

Re: 1.509.4 backporting

Since 1.509.4 is still a work in progress, please consider JENKINS-19418 for backporting. It not only makes the API unrealiable, it also randomly breaks builds that use Copy Artifact build steps. The fix in PR 928 looks pretty safe as well. Regards, Daniel -- You received this message becaus

Re: 1.509.4 backporting

Can we get http://jenkins-ci.org/commit/jenkins/0ab79882978292f3751be8e0acf5ae7edb0751f1backported (i.e. https://issues.jenkins-ci.org/browse/JENKINS-12629) without waiting for the 2-week window. This is IMHO a valid exception to the 2 week window for the following reasons: * X509TrustManager exte

Re: 1.509.4 backporting

I forgot to mark the rejected issues after 1.509.3. I do not promise I will have time to review and backport all new candidates. Btw.: What do core think, are the LTS releases becoming too huge? We seem to sustain the quality lever for now, IMO. -- oliver -- You received this message becau

Re: 1.509.4 backporting

Hi, I nominated several more issues fixed since 1.509 for backporting to LTS. Schedule permitting, it'd probably make sense if someone could take a look and consider whether to include those, especially if 1.509.4 is the last LTS based on 1.509. By the way, what happened to the label 1.xxx.y-r

Re: 1.509.4 backporting

On Fri, Sep 20, 2013 at 8:20 AM, ogondza wrote: > Can we produce 1.509.4-JENKINS-14362-jzlib before 1.509.4 or even before > 1.509.4-rc so we > can benefit from the reports? Not sure which reports you mean. We already have reports about JENKINS-14362 coming in from trunk users and 1.509.2-JENKIN

Re: 1.509.4 backporting

I would really like to avoid 1.509.5 . Can we produce 1.509.4-JENKINS-14362-jzlib before 1.509.4 or even before 1.509.4-rc so we can benefit from the reports? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group

Re: 1.509.4 backporting

Jesse under https://github.com/jenkinsci/jenkins/commit/a021fe5c2422c47d977d7937f4e01483f121b777: > @olivergondza if you are backporting this then I would urge you to also > backport > https://github.com/jenkinsci/jenkins/commit/b02d45737e4eb7a0455ebe192271cf76bbf271e0 > > from [JENKINS-19473

RE: 1.509.4 backporting

Given I have hit this (Kohsuke raised it on our behalf) and the only way out of it is to restart Jenkins I would +1 it. YMMV :) Are there any votes for JENKINS-18589? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: 1.509.4 backporting

On Thu, Sep 19, 2013 at 11:42 AM, James Nord (jnord) wrote: > Given I have hit [JENKINS-18589…] and the only way out of it is to restart > Jenkins I would +1 it. FWIW, another customer of ours seems to have just been hit by a variant of this, triggered by a project rename. -- You received this

Re: 1.509.4 backporting

On Thu, Sep 19, 2013 at 11:14 AM, ogondza wrote: > backport complete and battle tested fixes if they arrive in time or revert > the original issue? You mean to defer JENKINS-14362 to say 1.509.5? Would be unfortunate but that is your judgement call to make. (I would produce a 1.509.4-JENKINS-143

Re: 1.509.4 backporting

Hi, I have backported all soaked candidates[1] but one (JENKINS-18589 Deadlock). As Jesse pointed out there are still two unresolved issues blocking JENKINS-15935 (Can't build using maven 3.1.0) to be part of 1.509.4. Are there any votes for JENKINS-18589? Thanks for all the suggestions. [1]

Re: 1.509.4 backporting

What about https://issues.jenkins-ci.org/browse/JENKINS-7291 ? Surprisingly, issue has not been marked as a lts-candidate. понедельник, 16 сентября 2013 г., 16:17:25 UTC+4 пользователь Jesse Glick написал: > > Looks like this has already begun. Can we make sure the label > 1.509.4-fixed gets app

Re: 1.509.4 backporting

It'd be great if you could consider the diagnostic improvements for JENKINS-8856 for backporting this time. I marked it `lts-candidate` for the diagnostics that actually allow troubleshooting. One could even consider the issue resolved, as any further occurrences of this error will also include

Re: 1.509.4 backporting

can this one now be integrated too? https://issues.jenkins-ci.org/browse/JENKINS-18441 its already marked as candidate... On 16.09.2013, at 23:24, Daniel Beck wrote: > Marked it as lts-candidate, so it'll show up for backporting. It might still > be too recent though. > > On 16.09.2013, at 23:

Re: 1.509.4 backporting

Marked it as lts-candidate, so it'll show up for backporting. It might still be too recent though. On 16.09.2013, at 23:12, Stefan Wolf wrote: > Hi, > > I would like to have https://github.com/jenkinsci/jenkins/pull/916 backported > (The commits are for issue 9637). > What would I have to do

Re: 1.509.4 backporting

Hi, I would like to have https://github.com/jenkinsci/jenkins/pull/916 backported (The commits are for issue 9637). What would I have to do to accomplish this? Best regards, Stefan Am Montag, 16. September 2013 14:41:05 UTC+2 schrieb ogondza: > > It is in sync now. > > > On Mon, Sep 16, 2013 at

Re: 1.509.4 backporting

It is in sync now. On Mon, Sep 16, 2013 at 2:17 PM, Jesse Glick wrote: > Looks like this has already begun. Can we make sure the label > 1.509.4-fixed gets applied to things that are backported? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Develo

1.509.4 backporting

Looks like this has already begun. Can we make sure the label 1.509.4-fixed gets applied to things that are backported? -- 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