-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: core
-
Labels:
-
Environment:Windows Server 2012 R2. Jenkins LTS 2.89.2
-
Similar Issues:
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:
- Install LTS 2.89.2
- Create new Freestyle project (ex. trigger_test-quiet_period)
- Add Quiet Period value to 30 (like in picture). (Quiet period can be found under Advanced.. button in general section)
- Save the job
- Build the job by using REST API or for the testing purpose just build directly from browser address bar
- http://<jenkins_address>/job/trigger_test-quiet_period/build
- Link can be found by hovering mouse cursor over
- Click proceed
- http://<jenkins_address>/job/trigger_test-quiet_period/build
- 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:
- Use same job as in step 1
- Change Quiet Period value to 30000. (Quiet period can be found under Advanced.. button in general section)
- Save the job
- Build the job by using REST API or for the testing purpose just build directly from browser address bar
- http://<jenkins_address>/job/trigger_test-quiet_period/build
- Link can be found by hovering mouse cursor over
- Click proceed
- http://<jenkins_address>/job/trigger_test-quiet_period/build
- 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
- relates to
-
JENKINS-44052 Incorrect usage of TimeDuration
-
- Resolved
-
- links to