• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • xvfb-plugin
    • None

      1. When configuring a project and looking at the advanced options for Xvfb, under Timeout in seconds, enter 5.
      2. Save and then navigate back to the project configuration page.
      3. Observe the Timeout in seconds is now 5000 (assuming for 5000 milliseconds).
      4. Keep the timeout at 5000, save again, and navigate back to the project configuration page.
      5. Observe the Timeout in seconds is now 5000000.

      This presents a problem because after initially setting the timeout to X seconds, it will be reset to X * 1000 seconds when returning and saving the configuration page. This results in Xvfb apparently hanging when it is really just waiting for the timeout to complete.

          [JENKINS-15174] Timeout option not retrieved correctly

          Code changed in jenkins
          User: Zoran Regvart
          Path:
          src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
          http://jenkins-ci.org/commit/xvfb-plugin/253a5bde656ee1ea883cdfb9410a37307a444381
          Log:
          JENKINS-15174 Timeout option not retrieved correctly

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/253a5bde656ee1ea883cdfb9410a37307a444381 Log: JENKINS-15174 Timeout option not retrieved correctly

          zregvart added a comment -

          Nice catch! Thank you for reporting. This should be fixed in 1.0.3.

          zregvart added a comment - Nice catch! Thank you for reporting. This should be fixed in 1.0.3.

          Thanks! For sure. I appreciate the quick fix as well.

          Daniel Piorkowski added a comment - Thanks! For sure. I appreciate the quick fix as well.

            zregvart zregvart
            piorkowd Daniel Piorkowski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: