Upgrading Jenkins LTS from 2.77 to 2.89 will change Quiet Period effective value from seconds into milliseconds.

      ex. 30 sec have to be configured now as 30000.

      Use Case:

      Set job Quiet Period value from UI. Trigger new build using REST API without delay parameter. 

      Reproduce steps:

      Step 1. Try Quiet period value 30:

      1. Install LTS 2.89.2
      2. Create new Freestyle project (ex. trigger_test-quiet_period)
      3. Add Quiet Period value to 30 (like in picture). (Quiet period can be found under Advanced.. button in general section)
      4. Save the job
      5. Build the job by using REST API or for the testing purpose just build directly from browser address bar
        1. http://<jenkins_address>/job/trigger_test-quiet_period/build 
          1. Link can be found by hovering mouse cursor over 
        2. Click proceed
      6. Go back to job page http://<jenkins_address>/view/test/job/trigger_test-quiet_period/

      Result: Quiet periods is 30ms. Build basically starts immediately.

      Excepted result: Quiet period is 30s
       

      Step 2. Try Quiet period value 30000:

      1. Use same job as in step 1
      2. Change Quiet Period value to 30000. (Quiet period can be found under Advanced.. button in general section)
      3. Save the job
      4. Build the job by using REST API or for the testing purpose just build directly from browser address bar
        1. http://<jenkins_address>/job/trigger_test-quiet_period/build
          1. Link can be found by hovering mouse cursor over 
        2. Click proceed
      5. Go back to job page http://<jenkins_address>/view/test/job/trigger_test-quiet_period/

      Result: Quiet periods is 30s

      Excepted result: Quiet period is over 8h

       

          [JENKINS-48770] Quiet period is in milliseconds

          Tapio Patteri created issue -
          Tapio Patteri made changes -
          Description Original: *Use Case:* Trigger new build using REST API

          Upgrading Jenkins LTS from {color:#14892c}2.77{color} to {color:#d04437}2.89{color} will change Quiet Period parameter from {color:#14892c}seconds{color} into {color:#d04437}milliseconds{color}.

          ex. 300 sec have to be configured as 300000.

           
          New: *Use Case:* Trigger new build using REST API

          Upgrading Jenkins LTS from {color:#14892c}2.77{color} to {color:#d04437}2.89{color} will change Quiet Period parameter from {color:#14892c}seconds{color} into {color:#d04437}milliseconds{color}.

          ex. 30 sec have to be configured as 30000.

           
          Tapio Patteri made changes -
          Link New: This issue relates to JENKINS-44052 [ JENKINS-44052 ]

          Tapio Patteri added a comment - - edited

          Maybe issue is related to this change https://issues.jenkins-ci.org/browse/JENKINS-44052

          Tapio Patteri added a comment - - edited Maybe issue is related to this change  https://issues.jenkins-ci.org/browse/JENKINS-44052

          Oleg Nenashev added a comment -

          FYI batmat

          Oleg Nenashev added a comment - FYI batmat

          oleg_nenashev tapiomtr imo the right behaviour is the one fixed in 2.89. If you expect seconds, you should suffix the call with 'secs'. 

          Baptiste Mathus added a comment - oleg_nenashev tapiomtr  imo the right behaviour is the one fixed in 2.89. If you expect seconds, you should suffix the call with 'secs'. 

          I mean: there was definitely a bug in the code which was mostly invisible since for instance the UI was suffixing already with 'secs'. Which would only surface in your case without it.

          Baptiste Mathus added a comment - I mean: there was definitely a bug in the code which was mostly invisible since for instance the UI was suffixing already with 'secs'. Which would only surface in your case without it.
          Baptiste Mathus made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Tapio Patteri added a comment - - edited

          Thank you for the answer batmat.

          EDIT2: 

          If implementation is correct then I think Quiet period comment box should be fixed from "Number of seconds" to "Number of seconds when you are using upstream job etc. but when you are using documented REST API numbers handled as milliseconds instead of seconds" or something better because now these Quiet period box numbers working differently in different use cases.

          Tapio Patteri added a comment - - edited Thank you for the answer  batmat . EDIT2:  If implementation is correct then I think Quiet period comment box should be fixed from "Number of seconds" to "Number of seconds when you are using upstream job etc. but when you are using documented REST API numbers handled as milliseconds instead of seconds" or something better because now these Quiet period box numbers working differently in different use cases.

          Tapio Patteri added a comment - - edited

          If it's intended behavior that Quiet Period box numbers means different when using REST API, at least it should be documented.

          Tapio Patteri added a comment - - edited If it's intended behavior that Quiet Period box numbers means different when using REST API, at least it should be documented.
          Tapio Patteri made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            fcojfernandez Francisco Fernández
            tpatteri Tapio Patteri
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: