Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14105

Build timeout plugin 1.9 always sets timeout period to 3 minutes

      The Build Timeout plugin version 1.9 appears to rewrite the timeout period to 3 minutes, regardless of what is specified.

          [JENKINS-14105] Build timeout plugin 1.9 always sets timeout period to 3 minutes

          Here are the two bug reports as seen on jenkinsci-users:

          Report 1
          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 until the triggered projects finish their builds" specified.

          When I upgraded to Build timeout plugin 1.9, job B was timed out after 3 minutes, and when I looked, B's config had been rewritten to have a timeout of 3 minutes.

          Report 2
          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.

          Matthew Webber added a comment - Here are the two bug reports as seen on jenkinsci-users: Report 1 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 until the triggered projects finish their builds" specified. When I upgraded to Build timeout plugin 1.9, job B was timed out after 3 minutes, and when I looked, B's config had been rewritten to have a timeout of 3 minutes. Report 2 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.

          Stephane Odul added a comment -

          I see the same exact issue, I'm reverting the plugin to 1.8 for now.

          Stephane Odul added a comment - I see the same exact issue, I'm reverting the plugin to 1.8 for now.

          Code changed in jenkins
          User: Seiji Sogabe
          Path:
          src/main/java/hudson/plugins/build_timeout/BuildTimeoutWrapper.java
          http://jenkins-ci.org/commit/build-timeout-plugin/f1ca983dea997e5cf8311e5f77383c73f0493648
          Log:
          [FIXED JENKINS-14105] Build timeout plugin 1.9 always sets timeout period to 3 minutes

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/build_timeout/BuildTimeoutWrapper.java http://jenkins-ci.org/commit/build-timeout-plugin/f1ca983dea997e5cf8311e5f77383c73f0493648 Log: [FIXED JENKINS-14105] Build timeout plugin 1.9 always sets timeout period to 3 minutes

          This is happening again in 1.11.

          Not matter whether if you've selected Absolute Timeout or not, it's value is fixed a 3 minutes.

          Also it seems to be applying the absolute timeout to build even when it's not selected.

          Let me know if you need more infromation.

          Jonathan Kirkham added a comment - This is happening again in 1.11. Not matter whether if you've selected Absolute Timeout or not, it's value is fixed a 3 minutes. Also it seems to be applying the absolute timeout to build even when it's not selected. Let me know if you need more infromation.

          I have been running with 1.11 for a while, and have not seen this problem reoccur.
          Does it happen with all jobs?

          Matthew Webber added a comment - I have been running with 1.11 for a while, and have not seen this problem reoccur. Does it happen with all jobs?

          Jonathan Kirkham added a comment - - edited

          The 3 minutes being unchangeable is for all jobs.

          The absolute timeout being abling even when it's not selected only seems to be affect certain builds. For example, I have one node of a Matrix job where this is happening but not the other three.

          Background: I upgraded to 1.11 to enable the "fail the build" option (which works) and now I have discovered this problem.

          Jonathan Kirkham added a comment - - edited The 3 minutes being unchangeable is for all jobs. The absolute timeout being abling even when it's not selected only seems to be affect certain builds. For example, I have one node of a Matrix job where this is happening but not the other three. Background: I upgraded to 1.11 to enable the "fail the build" option (which works) and now I have discovered this problem.

          sogabe added a comment -

          uum... I can not reproduce this problem.
          If you specify "absolute timeout" less than 3 minutes, then This plugin saved it as 3 minitues.

          sogabe added a comment - uum... I can not reproduce this problem. If you specify "absolute timeout" less than 3 minutes, then This plugin saved it as 3 minitues.

          sogabe added a comment -

          If reproduced, please reopen.

          sogabe added a comment - If reproduced, please reopen.

            sogabe sogabe
            mwebber Matthew Webber
            Votes:
            6 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: