Re: Jenkins 2.73.1 LTS RC testing started

> On 14. Sep 2017, at 18:50, Daniel Beck wrote: > > We have some new information on the issue Mark discovered during testing: > > https://issues.jenkins-ci.org/browse/JENKINS-46754 (latest comments) > > Oliver, would you support integrating a fix for that into stable-2.73,

Re: Jenkins 2.73.1 LTS RC testing started

> On 14. Sep 2017, at 07:42, ogondza wrote: > > Agreed on the meeting the release will be cut with the regression compared to > 2.60 line (with remoting 3.10) and Jenkins docker container will be updated > not to be impacted. The proper fix will target 2.73.2. We have some

Re: Jenkins 2.73.1 LTS RC testing started

Hello, I have release Remoting 3.12 with a fix. I hope to get it integrated into the weekly, PR: https://github.com/jenkinsci/jenkins/pull/3025 BR, Oleg 2017-09-14 7:42 GMT+02:00 ogondza : > Agreed on the meeting the release will be cut with the regression compared > to 2.60

Re: Jenkins 2.73.1 LTS RC testing started

Agreed on the meeting the release will be cut with the regression compared to 2.60 line (with remoting 3.10) and Jenkins docker container will be updated not to be impacted. The proper fix will target 2.73.2. -- oliver -- You received this message because you are subscribed to the Google

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 10:51 AM, Oleg Nenashev wrote: > My proposal would be to spin 3.10.1 only with this fix. In such case we > could delay LTS release till Friday and do some spot-checks of the new RC > candidates with the fix. +1 -- You received this message

Re: Jenkins 2.73.1 LTS RC testing started

I will likely miss the beginning of the Governance meeting today unless my plane lands super-fast. My vote: I agree that the issue is serious enough to delay the release. My proposal would be to spin 3.10.1 only with this fix. In such case we could delay LTS release till Friday and do some

Re: Jenkins 2.73.1 LTS RC testing started

> On 13. Sep 2017, at 16:06, Jesse Glick wrote: > > IIUC we can simply patch the image to either have a writable `$HOME`, > or specify an explicit `-workDir`, so that most users are not > affected—right? > Right now, I don't think 2.73.1 is ready for release due to this

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 8:24 AM Oleg Nenashev wrote: > Yes. Regression is in 3.10, but it has not been fixed in 3.11 > Release of 3.12 is required to fix this regression. > > My plan is to spin it tomorrow. > > Regarding just updating LTS, note that 3.11 includes new API

Re: Jenkins 2.73.1 LTS RC testing started

Yes. Regression is in 3.10, but it has not been fixed in 3.11 Release of 3.12 is required to fix this regression. My plan is to spin it tomorrow. Regarding just updating LTS, note that 3.11 includes new API changes. Although they a minor, I am not sure that just bumping the version is safe

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 10:20 AM, Mark Waite wrote: > Did I misunderstand Oleg's earlier statement? He said there was a regression in 3.10. He did not say it was fixed in 3.11. The proposed fix is still under review. -- You received this message because you are

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 8:16 AM Jesse Glick wrote: > On Wed, Sep 13, 2017 at 10:11 AM, Mark Waite > wrote: > > there is a known regression in remoting 3.10 which is fixed in > > remoting 3.11. > > Which? Not JENKINS-45755. > > Did I misunderstand

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 10:11 AM, Mark Waite wrote: > there is a known regression in remoting 3.10 which is fixed in > remoting 3.11. Which? Not JENKINS-45755. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Jenkins 2.73.1 LTS RC testing started

2017-09-13 16:06 GMT+02:00 Jesse Glick : > On Wed, Sep 13, 2017 at 8:26 AM, Vincent Latombe > wrote: > >> Is this going to be a problem in the official Jenkins Docker images? > > > > I created a reproducer (in the ticket) using only the official

Re: Jenkins 2.73.1 LTS RC testing started

I'd prefer that we deliver 2.73.1 LTS with remoting 3.11. I don't see the benefit of remaining with 3.10. The cases I tested showed no difference between remoting 3.10 and remoting 3.11, and there is a known regression in remoting 3.10 which is fixed in remoting 3.11. Mark Waite On Wed, Sep

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 13, 2017 at 8:26 AM, Vincent Latombe wrote: >> Is this going to be a problem in the official Jenkins Docker images? > > I created a reproducer (in the ticket) using only the official Jenkins > Docker image. IIUC we can simply patch the image to either have

Re: Jenkins 2.73.1 LTS RC testing started

Hi, In case the issue is finally considered severe enough to be included in .1, I just wanted to point out that we completed out testing with the rc before remoting was retracted from 3.11 to 3.10 and found no issues, in case it helps in deciding whether (and where) a backport is needed. Thanks

Re: Jenkins 2.73.1 LTS RC testing started

2017-09-13 12:40 GMT+02:00 Daniel Beck : > > > On 13. Sep 2017, at 12:11, Vincent Latombe > wrote: > > > > Docker environment > > Is this going to be a problem in the official Jenkins Docker images? I created a reproducer (in the ticket) using only

Re: Jenkins 2.73.1 LTS RC testing started

> On 13. Sep 2017, at 12:11, Vincent Latombe wrote: > > Docker environment Is this going to be a problem in the official Jenkins Docker images? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: Jenkins 2.73.1 LTS RC testing started

Regarding JENKINS-45755 , affected users will be those running Jenkins with a non-writable user home directory (like a service user for the issue logger). This is a more common situation in Docker environment, in cases you have to run Jenkins as

Re: Jenkins 2.73.1 LTS RC testing started

Hi, Unfortunately I had no time to deploy the RC on my test instance due to conferences. So I have no testing results Regarding Remoting, there is a regression in 3.10 - JENKINS-45755 . Effectively it prevents channel from being established

Re: Jenkins 2.73.1 LTS RC testing started

Mark, Thanks for the extensive testing. Despite the fact his was not confirmed as remoting problem, I am leaving the remoting version bump reverted so the version will be 3.10 in LTS 2.73.1 and the candidate will be reconsidered for .2. So the current RC is what we will release on Wednesday in

Re: Jenkins 2.73.1 LTS RC testing started

I reported JENKINS-46754 - 2.73.1 RC agent won't start if using ed25519 passphrase protected key and have explored it further. The bug is unrelated to the remoting version. The change which Oliver made (at my request) to switch from remoting

Re: Jenkins 2.73.1 LTS RC testing started

I have reverted remoting back to version 3.10 and pushed another RC asking Mark to retest. Relevant issue https://issues.jenkins-ci.org/browse/JENKINS-46754 -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Jenkins 2.73.1 LTS RC testing started

On Wed, Sep 6, 2017 at 11:47 AM Jesse Glick wrote: > On Wed, Sep 6, 2017 at 10:26 AM, Mark Waite > wrote: > > I've seen two cases where JGit based ssh protocol cloning of a remote > > repository fails on 2.73.1 release candidate when it

Re: Jenkins 2.73.1 LTS RC testing started

Oliver, I'm seeing behavioral differences in ssh between the 2.73.1 release candidate. For example, one of my agents using an ed25519 private key starts correctly from 2.60.3, but does not start from 2.73.1 release candidate. I've seen two cases where JGit based ssh protocol cloning of a remote

Jenkins 2.73.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Release is scheduled for 2017-09-13. Report your findings in this thread or on the test plan wiki page. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.73.1/jenkins.war Check community maintained LTS