Pat, I have not used the plugin before. There is an open bug against the build-timeout plugin complaining that no output is written to the console log when a build is killed for taking too long. So, when a job is killed, the developer looking at the console output would have to realize that the job was running for a long time and assume it was probably killed because of that. Granularity is at the Jenkins job level.
Maybe it would make sense to do both. The verification builds are running prior to code review. We could set the Jenkins build-timeout plugin to catch cases where the build runs for 30 minutes or more because someone forgot to use "timeout -k", but should have. That is well outside the current 6 sigma build time range, and could be adjusted upwards if builds start taking significantly longer. Bill. From: Lankswert, Patrick Sent: Friday, March 20, 2015 1:04 PM To: Dieter, William R; iotivity-dev at lists.iotivity.org Subject: RE: Jenkins build timeout plugin Bill, I would like to see that and/or wrapping steps with 'timeout' with '-k' so that the script can limit individual steps with a finer grain control. Which direction provides the greatest detail to failures when the time is exceeded? Pat From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] 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 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 attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150324/0db96c58/attachment.html>
