I have opened https://issues.jenkins-ci.org/browse/JENKINS-14105 for this bug.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jason Swager
Sent: 14 June 2012 15:26
To: jenkinsci-users@googlegroups.com
Subject: Re: Bug in latest release of Build
>
> Seeing similar behavior. Actually, I'm seeing worse. Regardless of what
> value I specify, it looks like a 3 minute value is all that every gets
> saved.
I haven't opened a ticket for this yet, but there is a significant bug in Build
timeout plugin 1.9.
I have job A, with a timeout of 3 minutes. A (using the parameterized plugin)
does a "Trigger/call builds on other projects" to job B, which has a timeout of
60 minutes. A does _not_ have "Block
