[2.0] slipping date

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[2.0] slipping date

Kohsuke Kawaguchi
Administrator
In today's 2.0 status check call, Daniel Beck as 2.0 release manager had raised that we still have too many issues in flight and it's unrealistic to expect that we can fix them all in RC. So we decided to add one more week till RC.

Then we realized that this is exactly the same thing that happened with beta. So it looks like it'd be a reasonable estimate that RC to release is going to need 2 weeks, too. That way we don't have to make a fool of ourselves by slipping it once again two weeks from now.

That brings the updated time line to ...
  • April 6: Create first release candidate (RC)
  • April 20: Create 2.0 proper release with last RC
  • April 26: More coordinated launch marketing activities commence
For the up-to-date information, please check the 2.0 Wiki page. My apologies for any inconvenience this may cause to anyone.

--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4wkNXrsM2U1XDNrZ1MNBP0uuMmzHi0%2BW5FMFiwKciA15w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Kohsuke Kawaguchi
Administrator
(For dev list...)

This impacts the branching & 1.x release freeze plan announced by Daniel earlier, too.
  • April 3: 1.656 release, which will be the last 1.x release
  • April 6: RC.
    master will be merged into 2.0. Ideally we're not going to merge crazy stuff into 'master' between now and next Wednesday to keep the risk of the 2.0 RC being terrible low. Any unmerged pull requests against '2.0' will be closed, and '2.0' will be merged into 'master'. This means that from that point on, anything happening on the 'master' branch will be released as 2.1, as it makes no sense to continue releasing 1.x weeklies while 2.0 code is frozen and we're preparing the release.
  • April 10: weekly release will be skipped
  • Apirl 17: weekly release will be skipped
  • April 20: 2.0 GA
  • April 26: More coordinated launch marketing activities commence
  • May 1:  2.1 and weekly release resumes

Also, we agreed that "Major" and above fixes are only allowed until March 30, "Critical" and above are allowed only until RC, and only "Blocker" past that point, so that we do march toward the conversion and prevent the extra time from getting used on random fixes that end up destabilzing.

Thanks for focusing the effort around 2.0, especially those of you who are working on fixes that are targeted for 2.0. Others, please continue to kick the tire and report problems you find!


2016-03-28 17:45 GMT-07:00 Kohsuke Kawaguchi <[hidden email]>:
In today's 2.0 status check call, Daniel Beck as 2.0 release manager had raised that we still have too many issues in flight and it's unrealistic to expect that we can fix them all in RC. So we decided to add one more week till RC.

Then we realized that this is exactly the same thing that happened with beta. So it looks like it'd be a reasonable estimate that RC to release is going to need 2 weeks, too. That way we don't have to make a fool of ourselves by slipping it once again two weeks from now.

That brings the updated time line to ...
  • April 6: Create first release candidate (RC)
  • April 20: Create 2.0 proper release with last RC
  • April 26: More coordinated launch marketing activities commence
For the up-to-date information, please check the 2.0 Wiki page. My apologies for any inconvenience this may cause to anyone.

--
Kohsuke Kawaguchi



--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z2tXarucJbeQcUGdMAS%2ByMvV%3DvpdKb9y%3DSjgcw2VPhmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Kanstantsin Shautsou-2
So, everybody would have 1.x without fixes for 2 months and 2.x that would be unstable? 

On Tuesday, March 29, 2016 at 3:54:36 AM UTC+3, Kohsuke Kawaguchi wrote:
(For dev list...)

This impacts <a href="https://groups.google.com/d/msg/jenkinsci-dev/l6hjg66-TGI/g6dVRiFLAQAJ" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msg/jenkinsci-dev/l6hjg66-TGI/g6dVRiFLAQAJ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msg/jenkinsci-dev/l6hjg66-TGI/g6dVRiFLAQAJ&#39;;return true;">the branching & 1.x release freeze plan announced by Daniel earlier, too.
  • April 3: 1.656 release, which will be the last 1.x release
  • April 6: RC.
    master will be merged into 2.0. Ideally we're not going to merge crazy stuff into 'master' between now and next Wednesday to keep the risk of the 2.0 RC being terrible low. Any unmerged pull requests against '2.0' will be closed, and '2.0' will be merged into 'master'. This means that from that point on, anything happening on the 'master' branch will be released as 2.1, as it makes no sense to continue releasing 1.x weeklies while 2.0 code is frozen and we're preparing the release.
  • April 10: weekly release will be skipped
  • Apirl 17: weekly release will be skipped
  • April 20: 2.0 GA
  • April 26: More coordinated launch marketing activities commence
  • May 1:  2.1 and weekly release resumes

Also, we agreed that "Major" and above fixes are only allowed until March 30, "Critical" and above are allowed only until RC, and only "Blocker" past that point, so that we do march toward the conversion and prevent the extra time from getting used on random fixes that end up destabilzing.

Thanks for focusing the effort around 2.0, especially those of you who are working on fixes that are targeted for 2.0. Others, please continue to kick the tire and report problems you find!


2016-03-28 17:45 GMT-07:00 Kohsuke Kawaguchi <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zNJoKCLdAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">k...@...>:
In today's 2.0 status check call, Daniel Beck as 2.0 release manager had raised that we still have <a href="https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=81" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fissues.jenkins-ci.org%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D81\46sa\75D\46sntz\0751\46usg\75AFQjCNHpErLuhjVc20l7fpsUn-3bx-QTkw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fissues.jenkins-ci.org%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D81\46sa\75D\46sntz\0751\46usg\75AFQjCNHpErLuhjVc20l7fpsUn-3bx-QTkw&#39;;return true;">too many issues in flight and it's unrealistic to expect that we can fix them all in RC. So we decided to add one more week till RC.

Then we realized that this is exactly the same thing that happened with beta. So it looks like it'd be a reasonable estimate that RC to release is going to need 2 weeks, too. That way we don't have to make a fool of ourselves by slipping it once again two weeks from now.

That brings the updated time line to ...
  • April 6: Create first release candidate (RC)
  • April 20: Create 2.0 proper release with last RC
  • April 26: More coordinated launch marketing activities commence
For the up-to-date information, please check <a href="https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FJenkins%2B2.0\46sa\75D\46sntz\0751\46usg\75AFQjCNFHJ3cl99jNKsX4nETtmVQ1GTCTDg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FJenkins%2B2.0\46sa\75D\46sntz\0751\46usg\75AFQjCNFHJ3cl99jNKsX4nETtmVQ1GTCTDg&#39;;return true;">the 2.0 Wiki page. My apologies for any inconvenience this may cause to anyone.

--
Kohsuke Kawaguchi



--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6ffecd61-b143-4bf6-82ab-01399d81e1d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Daniel Beck

On 05.04.2016, at 02:06, Kanstantsin Shautsou <[hidden email]> wrote:

> 1.x without fixes for 2 months and 2.x that would be unstable?

Not sure what you're referring to. As you can see in the plan posted by Kohsuke, we'll skip just two weekly releases, something we did around New Year's without notable issues, and before then in November. I can't remember a single substantial complaint. "We don't get to upgrade Jenkins often enough" is a complaint I don't expect to hear any time soon.

And the reason we're skipping a few weeklies is to ensure as much as we can that 2.0 will not be a terrible release because it pulls in a broken change from master at the last minute. AFAICT it gets much more testing than any weekly release of Jenkins in recent history, probably even LTS releases.

And if there's actually a critical bug in 1.656 (too recent to tell from feedback), we'll find a way to post a 1.657 with a bug fix for it.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/02F33C06-9DA6-4B83-8301-6F04FB1217C9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Daniel Beck
In reply to this post by Kohsuke Kawaguchi

On 29.03.2016, at 02:54, Kohsuke Kawaguchi <[hidden email]> wrote:

> • April 6: RC.
> master will be merged into 2.0. Ideally we're not going to merge crazy stuff into 'master' between now and next Wednesday to keep the risk of the 2.0 RC being terrible low. Any unmerged pull requests against '2.0' will be closed, and '2.0' will be merged into 'master'. This means that from that point on, anything happening on the 'master' branch will be released as 2.1, as it makes no sense to continue releasing 1.x weeklies while 2.0 code is frozen and we're preparing the release.

Hi everyone,

KK is starting to release the 2.0 RC now.

Given the late hour, I will merge 2.0 into master tomorrow.

Daniel

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3D334C94-015C-48DC-9D99-E4BFFA9E6469%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Daniel Beck

On 07.04.2016, at 02:37, Daniel Beck <[hidden email]> wrote:

> Given the late hour, I will merge 2.0 into master tomorrow.

The merge commit is here: https://github.com/daniel-beck/jenkins/commit/1fe9cf7b7ada45230f2bc5b8e2f1bdb93175ff9f

If you'd like to give it a final review, the time to do so is right now. I'll hold off pushing this for a few hours (and I won't do additional rounds if I have to resolve a conflict later). Please note that any findings will need to be addressed in followup changes, likely towards 2.1.

A reminder:

The version 2.0 will be released from the '2.0' branch. Any changes to 'master' will be targeting 2.1 (I'll adjust the POM version later).

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/41A4284B-F8C7-4B43-B413-3E1CD1CC942A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Daniel Beck
I pushed the merge to 'master'. So anything targeting 2.1+ can be now proposed in pull requests to that branch.

Anything happening on '2.0' branch will be limited to critical fixes for the 2.0 release specifically.

On 07.04.2016, at 12:08, Daniel Beck <[hidden email]> wrote:

>
> On 07.04.2016, at 02:37, Daniel Beck <[hidden email]> wrote:
>
>> Given the late hour, I will merge 2.0 into master tomorrow.
>
> The merge commit is here: https://github.com/daniel-beck/jenkins/commit/1fe9cf7b7ada45230f2bc5b8e2f1bdb93175ff9f
>
> If you'd like to give it a final review, the time to do so is right now. I'll hold off pushing this for a few hours (and I won't do additional rounds if I have to resolve a conflict later). Please note that any findings will need to be addressed in followup changes, likely towards 2.1.
>
> A reminder:
>
> The version 2.0 will be released from the '2.0' branch. Any changes to 'master' will be targeting 2.1 (I'll adjust the POM version later).
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/41A4284B-F8C7-4B43-B413-3E1CD1CC942A%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6E009640-EE63-44B0-ABEE-2E35BBB04949%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Robert Sandell-2
Where is the RC?

On Thu, Apr 7, 2016 at 4:26 PM, Daniel Beck <[hidden email]> wrote:
I pushed the merge to 'master'. So anything targeting 2.1+ can be now proposed in pull requests to that branch.

Anything happening on '2.0' branch will be limited to critical fixes for the 2.0 release specifically.

On 07.04.2016, at 12:08, Daniel Beck <[hidden email]> wrote:

>
> On 07.04.2016, at 02:37, Daniel Beck <[hidden email]> wrote:
>
>> Given the late hour, I will merge 2.0 into master tomorrow.
>
> The merge commit is here: https://github.com/daniel-beck/jenkins/commit/1fe9cf7b7ada45230f2bc5b8e2f1bdb93175ff9f
>
> If you'd like to give it a final review, the time to do so is right now. I'll hold off pushing this for a few hours (and I won't do additional rounds if I have to resolve a conflict later). Please note that any findings will need to be addressed in followup changes, likely towards 2.1.
>
> A reminder:
>
> The version 2.0 will be released from the '2.0' branch. Any changes to 'master' will be targeting 2.1 (I'll adjust the POM version later).
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/41A4284B-F8C7-4B43-B413-3E1CD1CC942A%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6E009640-EE63-44B0-ABEE-2E35BBB04949%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1FthX62gY0rcALBhpKp-JdZDb4gso0gmEky-MvaSWUyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Daniel Beck

On 07.04.2016, at 17:16, Robert Sandell <[hidden email]> wrote:

> Where is the RC?

Same URL as the betas, except for Docker and that's listed on https://hub.docker.com/r/jenkinsci/jenkins/tags/ -- I just need to get the 2.0 page updated and submit the blog post. Haven't had the time to do so yet, unfortunately.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15137931-8AD6-4132-9176-DF6F439977F5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
I'm trying to diagnose the OOME in tests on
https://ci.jenkins-ci.org/job/jenkins_main_trunk after merging 2.0
into master.
Running tests locally.

On Thu, Apr 7, 2016 at 5:22 PM, Daniel Beck <[hidden email]> wrote:

>
> On 07.04.2016, at 17:16, Robert Sandell <[hidden email]> wrote:
>
>> Where is the RC?
>
> Same URL as the betas, except for Docker and that's listed on https://hub.docker.com/r/jenkinsci/jenkins/tags/ -- I just need to get the 2.0 page updated and submit the blog post. Haven't had the time to do so yet, unfortunately.
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15137931-8AD6-4132-9176-DF6F439977F5%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRKhd%3D2ZW48%3D3GPnLyDFgfiwqqTbzGv0JWzPPENHtGQWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
The build is using JDK 7, could it be configured to use JDK 8?
(https://ci.jenkins-ci.org/job/jenkins_pipeline/branch/2.0 is stable
with JDK 8)

On Fri, Apr 8, 2016 at 10:18 AM, Antonio Muñiz <[hidden email]> wrote:

> I'm trying to diagnose the OOME in tests on
> https://ci.jenkins-ci.org/job/jenkins_main_trunk after merging 2.0
> into master.
> Running tests locally.
>
> On Thu, Apr 7, 2016 at 5:22 PM, Daniel Beck <[hidden email]> wrote:
>>
>> On 07.04.2016, at 17:16, Robert Sandell <[hidden email]> wrote:
>>
>>> Where is the RC?
>>
>> Same URL as the betas, except for Docker and that's listed on https://hub.docker.com/r/jenkinsci/jenkins/tags/ -- I just need to get the 2.0 page updated and submit the blog post. Haven't had the time to do so yet, unfortunately.
>>
>> --
>> 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 [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15137931-8AD6-4132-9176-DF6F439977F5%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzSpXSCWUpJSD2Wq1un-Gf%3DGESZYBv%3D7PqRufDdRVZDwMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Arnaud Héritier
Why do we use Java 8 for CI ?
Java 7 is the oldest version we are supporting for now it must run with it :(

On Fri, Apr 8, 2016 at 10:24 AM, Antonio Muñiz <[hidden email]> wrote:
The build is using JDK 7, could it be configured to use JDK 8?
(https://ci.jenkins-ci.org/job/jenkins_pipeline/branch/2.0 is stable
with JDK 8)

On Fri, Apr 8, 2016 at 10:18 AM, Antonio Muñiz <[hidden email]> wrote:
> I'm trying to diagnose the OOME in tests on
> https://ci.jenkins-ci.org/job/jenkins_main_trunk after merging 2.0
> into master.
> Running tests locally.
>
> On Thu, Apr 7, 2016 at 5:22 PM, Daniel Beck <[hidden email]> wrote:
>>
>> On 07.04.2016, at 17:16, Robert Sandell <[hidden email]> wrote:
>>
>>> Where is the RC?
>>
>> Same URL as the betas, except for Docker and that's listed on https://hub.docker.com/r/jenkinsci/jenkins/tags/ -- I just need to get the 2.0 page updated and submit the blog post. Haven't had the time to do so yet, unfortunately.
>>
>> --
>> 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 [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/15137931-8AD6-4132-9176-DF6F439977F5%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzSpXSCWUpJSD2Wq1un-Gf%3DGESZYBv%3D7PqRufDdRVZDwMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8tmaHRM1JLvhOEV-8KE4AXmDmx7xqcj6PVwohcM67iOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
On Fri, Apr 8, 2016 at 10:32 AM, Arnaud Héritier <[hidden email]> wrote:
> Java 7 is the oldest version we are supporting for now it must run with it
> :(


`<java.level>7</java.level>` is set anyways. So building with JDK 8
should be fine.
BTW the test suite ran successfully in my local box - max memory
consumption during tests: 500MB - (JDK 8, Maven 3.3.3)

But before changing anything, could someone check that `celery` node
is ok? Last time Daniel checked there were a lot of zombie processes
eating the memory (which leaded to OOM errors in new builds).

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQmaq1AA_CF7EL89K009gTXVQ52p8D5W1XXwOj6kYxgVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Kanstantsin Shautsou-2
Limit threading in build and check what you did with pom and threading in pom/test plugins.

> On Apr 8, 2016, at 11:59, Antonio Muñiz <[hidden email]> wrote:
>
> On Fri, Apr 8, 2016 at 10:32 AM, Arnaud Héritier <[hidden email]> wrote:
>> Java 7 is the oldest version we are supporting for now it must run with it
>> :(
>
>
> `<java.level>7</java.level>` is set anyways. So building with JDK 8
> should be fine.
> BTW the test suite ran successfully in my local box - max memory
> consumption during tests: 500MB - (JDK 8, Maven 3.3.3)
>
> But before changing anything, could someone check that `celery` node
> is ok? Last time Daniel checked there were a lot of zombie processes
> eating the memory (which leaded to OOM errors in new builds).
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQmaq1AA_CF7EL89K009gTXVQ52p8D5W1XXwOj6kYxgVg%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8D9D26AD-D27E-48F2-9E1C-24A21DFE1E50%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
<[hidden email]> wrote:
> check what you did with pom and threading in pom/test plugins.

Nothing was done, just -Xmx1g (which is not required IMO).

I think celery is not being able to manage the load and that's the
root cause of OOM errors. Arnaud just checked that the physical memory
was completely full some minutes ago (so 2.0 builds are getting OOM
even before hitting their 1GB limit).

I guess the number of concurrent builds increased in the last months?

If the problem persists, this would need to be reopen/merged to give
us some light: https://github.com/jenkinsci/jenkins/pull/2220

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
https://ci.jenkins-ci.org/job/jenkins_main_trunk/4555 is running. No
memory issues so far, but a test seems to be blocked for some other
reason.

On Fri, Apr 8, 2016 at 12:21 PM, Antonio Muñiz <[hidden email]> wrote:

> On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
> <[hidden email]> wrote:
>> check what you did with pom and threading in pom/test plugins.
>
> Nothing was done, just -Xmx1g (which is not required IMO).
>
> I think celery is not being able to manage the load and that's the
> root cause of OOM errors. Arnaud just checked that the physical memory
> was completely full some minutes ago (so 2.0 builds are getting OOM
> even before hitting their 1GB limit).
>
> I guess the number of concurrent builds increased in the last months?
>
> If the problem persists, this would need to be reopen/merged to give
> us some light: https://github.com/jenkinsci/jenkins/pull/2220
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTYy7N%3DzBUM_jd3kCV-EdN-rYuArf79ZD4Brd0%3DNBg5JQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Kanstantsin Shautsou-2
In reply to this post by Antonio Muñiz

On Apr 8, 2016, at 13:21, Antonio Muñiz <[hidden email]> wrote:

On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
<[hidden email]> wrote:
check what you did with pom and threading in pom/test plugins.

Nothing was done, just -Xmx1g (which is not required IMO).

I think celery is not being able to manage the load and that's the
root cause of OOM errors. Arnaud just checked that the physical memory
was completely full some minutes ago (so 2.0 builds are getting OOM
even before hitting their 1GB limit).

I guess the number of concurrent builds increased in the last months?

If the problem persists, this would need to be reopen/merged to give
us some light: https://github.com/jenkinsci/jenkins/pull/2220
Your local runs wouldn’t reproduce anything because you have different hardware.
Check threading/forking in maven test plugins (surefire/failsafe). 

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B1984CD6-146D-4D84-B794-B47E1093C5CB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
One of the forked booters finished, the other one is blocked in a test. Any idea?

"Executing retainMasterLabelWhenNoSlaveDefined(jenkins.model.MasterBuildConfigurationTest)" prio=10 tid=0x00007f47f4007800 nid=0x3384 in Object.wait() [0x00007f47fbe88000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000c664a970> (a jenkins.model.Jenkins$8)
	at java.lang.Object.wait(Object.java:503)
	at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:267)
	- locked <0x00000000c664a970> (a jenkins.model.Jenkins$8)
	at jenkins.InitReactorRunner.run(InitReactorRunner.java:44)
	at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020)
	at jenkins.model.Jenkins.<init>(Jenkins.java:864)
	at hudson.model.Hudson.<init>(Hudson.java:85)
	at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:571)
	at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:358)
	at org.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:516)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)

On Fri, Apr 8, 2016 at 1:17 PM, Kanstantsin Shautsou <[hidden email]> wrote:

On Apr 8, 2016, at 13:21, Antonio Muñiz <[hidden email]> wrote:

On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
<[hidden email]> wrote:
check what you did with pom and threading in pom/test plugins.

Nothing was done, just -Xmx1g (which is not required IMO).

I think celery is not being able to manage the load and that's the
root cause of OOM errors. Arnaud just checked that the physical memory
was completely full some minutes ago (so 2.0 builds are getting OOM
even before hitting their 1GB limit).

I guess the number of concurrent builds increased in the last months?

If the problem persists, this would need to be reopen/merged to give
us some light: https://github.com/jenkinsci/jenkins/pull/2220
Your local runs wouldn’t reproduce anything because you have different hardware.
Check threading/forking in maven test plugins (surefire/failsafe). 

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B1984CD6-146D-4D84-B794-B47E1093C5CB%40gmail.com.

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



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQnJjqMXrboYpKzry9SCMg9K70Xm86%3DKqfwG3xiNfLJTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Kanstantsin Shautsou-2
Check dmesg, for OOM killer
On Apr 8, 2016, at 14:20, Antonio Muñiz <[hidden email]> wrote:

One of the forked booters finished, the other one is blocked in a test. Any idea?

"Executing retainMasterLabelWhenNoSlaveDefined(jenkins.model.MasterBuildConfigurationTest)" prio=10 tid=0x00007f47f4007800 nid=0x3384 in Object.wait() [0x00007f47fbe88000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000c664a970> (a jenkins.model.Jenkins$8)
	at java.lang.Object.wait(Object.java:503)
	at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:267)
	- locked <0x00000000c664a970> (a jenkins.model.Jenkins$8)
	at jenkins.InitReactorRunner.run(InitReactorRunner.java:44)
	at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020)
	at jenkins.model.Jenkins.<init>(Jenkins.java:864)
	at hudson.model.Hudson.<init>(Hudson.java:85)
	at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:571)
	at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:358)
	at org.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:516)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)

On Fri, Apr 8, 2016 at 1:17 PM, Kanstantsin Shautsou <[hidden email]> wrote:

On Apr 8, 2016, at 13:21, Antonio Muñiz <[hidden email]> wrote:

On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
<[hidden email]> wrote:
check what you did with pom and threading in pom/test plugins.

Nothing was done, just -Xmx1g (which is not required IMO).

I think celery is not being able to manage the load and that's the
root cause of OOM errors. Arnaud just checked that the physical memory
was completely full some minutes ago (so 2.0 builds are getting OOM
even before hitting their 1GB limit).

I guess the number of concurrent builds increased in the last months?

If the problem persists, this would need to be reopen/merged to give
us some light: https://github.com/jenkinsci/jenkins/pull/2220
Your local runs wouldn’t reproduce anything because you have different hardware.
Check threading/forking in maven test plugins (surefire/failsafe). 

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B1984CD6-146D-4D84-B794-B47E1093C5CB%40gmail.com.

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



--
Antonio Muñiz
Software Engineer
CloudBees, Inc.


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQnJjqMXrboYpKzry9SCMg9K70Xm86%3DKqfwG3xiNfLJTQ%40mail.gmail.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5364F770-AF06-40ED-9989-25BC56414AB4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [2.0] slipping date

Antonio Muñiz
On Fri, Apr 8, 2016 at 1:25 PM, Kanstantsin Shautsou
<[hidden email]> wrote:
> Check dmesg, for OOM killer


It's not a memory issue I believe, the test is just blocked for some reason.

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzR9-aH%3DXBNC_ZcHWp%3DQ9iJVixzDm3_m-XPzVRinaRvnnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
12