[dev] Jenkins build timeout plugin

2015-03-31 Thread Morrow, Joseph L
lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Jon A. Cruz Sent: Monday, March 30, 2015 5:54 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jenkins build timeout plugin Just FYI, from my experience 15 minutes is about the maximum that a commit-triggered build

[dev] Jenkins build timeout plugin

2015-03-30 Thread Keane, Erich
Thanks Bill! I highly doubt that even the 15mins is a reasonable amount of time, since we are no longer downloading the Arduino the time should be much less, but 90 should be a way more than required amount. Thanks! -Erich On Mon, 2015-03-30 at 21:03 +, Dieter, William R wrote: > It looks li

[dev] Jenkins build timeout plugin

2015-03-30 Thread Dieter, William R
It looks like there was another run away verification build today. I have had Linux Foundation install the Jenkins build timeout plug-in. As an initial starting point, I set the build timeout to 250% of the last 5 successful builds or 90 minutes (whichever comes first). Successful build times

[dev] Jenkins build timeout plugin

2015-03-30 Thread Jon A. Cruz
Just FYI, from my experience 15 minutes is about the maximum that a commit-triggered build should run. Getting it below 7 minutes seemed to be a good goal, with slightly diminishing returns kicking in after that. Skipping downloading (or at least grabbing from a local cache) should do a good job o

[dev] Jenkins build timeout plugin

2015-03-24 Thread Warburton, David
> On Mar 24, 2015, at 11:16 AM, Dieter, William R intel.com> wrote: > > I believe it was Sam and Erich were working on building the unit tests and > ran into the problem? > > > > Bill. > > > > From: Lankswert, Patrick > Sent: Tuesday, March 24, 2015 11:00 AM > To: Dieter, William R; io

[dev] Jenkins build timeout plugin

2015-03-24 Thread Dieter, William R
o:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Dieter, William R Sent: Friday, March 20, 2015 10:54 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Jenkins build timeout plugin There ha

[dev] Jenkins build timeout plugin

2015-03-24 Thread Lankswert, Patrick
ivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Dieter, William R Sent: Friday, March 20, 2015 10:54 AM To: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Jenkins build timeout plugin There ha

[dev] Jenkins build timeout plugin

2015-03-24 Thread Dieter, William R
0, 2015 10:54 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Jenkins build timeout plugin There has been an issue where a unit test hanging caused build jobs to back up on the CI server. Jenkins has a plug-in to kill build jobs that run longer

[dev] Jenkins build timeout plugin

2015-03-20 Thread Lankswert, Patrick
.@lists.iotivity.org [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Dieter, William R Sent: Friday, March 20, 2015 10:54 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Jenkins build timeout plugin There has been an issue where a unit test hanging caused build jobs

[dev] Jenkins build timeout plugin

2015-03-20 Thread Dieter, William R
There has been an issue where a unit test hanging caused build jobs to back up on the CI server. Jenkins has a plug-in to kill build jobs that run longer than a preset timeout. Does anyone know a reason not to install that plugin? Thanks, Bill. -- next part -- An HTML a