Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-releng-dev] Build schedule for M7 milestone week

> We will schedule builds 3 times per day on Monday and 3 times per
> day on Wednesday, with Tuesday being full test day. After Wednesday,
> will be on-demand for blocking/critical bug or regression fixes.

> Morning builds will be at 8 AM Eastern (for 4.2) and 10 AM Eastern (for 3.8)
> Evening builds will be a 6 PM, and 8 PM, for 4.2 and 3.8.
> Midday builds will be at 1 PM and 3 PM, for 4.2 and 3.8.


In case anyone noticed them missing, I feel asleep and forgot to change the crontab for this morning's 8 and 10 o'clock builds.

So, we'll have 2 builds today, and 3 on Wednesday. Do let me know if this messes up anyone's plans, so I can better understand impact (but, we had so many over the weekend, I'd think we'd be in pretty good shape for beginning Monday?)

Also, I never did get around to fixing/testing the "don't build if no changes" path, so you may see some builds occur with no changes to code. Since we are just building (not testing) I don't think this will hurt much, so will continue to focus on getting unit tests running on build.eclipse.org.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=377365
And improve the build logic after that.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=377666

Thanks,
 




Inactive hide details for David M Williams---04/25/2012 01:28:55 PM---Here is a summary of the build schedule we will follow foDavid M Williams---04/25/2012 01:28:55 PM---Here is a summary of the build schedule we will follow for M7's "final week", as discussed in status

From: David M Williams/Raleigh/IBM@IBMUS
To: platform-releng-dev@xxxxxxxxxxx,
Date: 04/25/2012 01:28 PM
Subject: [platform-releng-dev] Build schedule for M7 milestone week
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx





Here is a summary of the build schedule we will follow for M7's "final week", as discussed in status call today.

I will update the calendar [1] as well, but thought I'd post here, in prose, in case I misunderstood -- plus, I am going to add a small wrinkle.


For warm-ups, we'll build Thursday morning, and Friday morning, and Sunday evening.


We will schedule builds 3 times per day on Monday and 3 times per day on Wednesday, with Tuesday being full test day. After Wednesday, will be on-demand for blocking/critical bug or regression fixes.


In all cases, the 4.2 builds will be scheduled first, and then the 3.8 builds scheduled 2 hours later [we'd normally expect identical (or near identical) input, it is just offset so as to not swamp the build machine and signing queues].


Morning builds will be at 8 AM Eastern (for 4.2) and 10 AM Eastern (for 3.8)
Evening builds will be a 6 PM, and 8 PM, for 4.2 and 3.8.
Midday builds will be at 1 PM and 3 PM, for 4.2 and 3.8.


We may need to adjust as we get the unit tests running and see how they impact Hudson's overall utilization. Perhaps build/test 3.8 once per day, or something.


The N-builds will be turned off for this final week, starting Saturday (that is Friday nightly will be the last one).


The wrinkle: it occurred to me after the status meeting, is that I would like to turn on the "3 times per day schedule" (maybe more?) on Saturday and Sunday. BUT, still only take the final one on Sunday as the one official one to promote to "downloads" and leaving the others on build machine, unless someone requests otherwise. I want to do this to get a few runs through the parts of our automated scripts which are supposed to say "no changes detected, the such-and-such scheduled build was canceled". It might take a few passes to get that just right  [2]. So, I hope at least a few of those times over the weekend, in fact, no one will make any changes! :)  (or, if I really get into it, I might "simulate" by scheduling one for every hour or so, for testing).  So, Saturday and Sunday you might seeing some odd messages about scheduled builds being cancelled, or I builds being started or completed, but I'll try to figure out a way to divert those to test mail (though, I failed at that last time I tried).


If anyone has any corrections or questions, let me know.


[1]
http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html

[2]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=377666
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

GIF image


Back to the top