-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins core:
- 2.100
Pipeline plugins:
- workflow-job 2.17-durability-beta-1
- workflow-durable-task-step 2.17
- workflow-step-api 2.14
- workflow-support 2.17-durability-beta-1
- workflow-multibranch 2.17-durability-beta-1
- workflow-cps 2.43-durability-beta-1
- workflow-cps-global-lib 2.9
- workflow-basic-steps 2.6
- workflow-aggregator 2.5
- workflow-scm-step 2.6
- workflow-api 2.25-durability-beta-2
- docker-workflow 1.14
Client:
- Fedora Workstation 27
- Updated as of about a day ago
- Google Chrome Version 63.0.3239.108 (Official Build) (64-bit)Jenkins core: - 2.100 Pipeline plugins: - workflow-job 2.17-durability-beta-1 - workflow-durable-task-step 2.17 - workflow-step-api 2.14 - workflow-support 2.17-durability-beta-1 - workflow-multibranch 2.17-durability-beta-1 - workflow-cps 2.43-durability-beta-1 - workflow-cps-global-lib 2.9 - workflow-basic-steps 2.6 - workflow-aggregator 2.5 - workflow-scm-step 2.6 - workflow-api 2.25-durability-beta-2 - docker-workflow 1.14 Client: - Fedora Workstation 27 - Updated as of about a day ago - Google Chrome Version 63.0.3239.108 (Official Build) (64-bit)
Summary
Given a Global speed/durability setting of None: use pipeline default (MAX_SURVIVABILITY), it's possible to override a particular MBP project with a different run mode, such as PERFORMANCE_OPTIMIZED. If you remove this override, it disappears from the MBP's Configuration page as expected. Despite this, the branches will still run in PERFORMANCE_OPTIMIZED mode, I expected them to flip back to the Global default.
Prerequisites:
- Jenkins with the latest experiemtal update center versions of the Pipeline storage betas
- A MBP project with several branches, which include a Jenkinsfile that can be built successfully
Steps to recreate:
Probably the easiest way to describe this is using a table. I hope this makes sense to others in the same way it does to me.
| Step | Global Setting | MBP Setting | Expected | Actual |
|---|---|---|---|---|
| 1 | Set to None: use pipeline default (MAX_SURVIVABILITY) | No override | Pass: No override shown | |
| 2 | Verify DURABLE setting | MBP Config Page and individual branch View Config pages both show DURABLE | Pass | |
| 3 | Add Override and set to PERF | . | . | |
| 4 | Verify PERF setting | MBP Config Page and individual branch View Config pages both show PERF | Pass | |
| 5 | Run one build of DeclarativeParallels | Build runs in PERF | Pass | |
| 6 | Change to MIDDLE | Verify PERF setting still present | Global Setting in MIDDLE, MBP setting still in PERF. | Pass |
| 7 | Remove override, save | Override should be gone | Pass: Override is gone | |
| 8 | Check setting on individual branches | Override should be gone | Fail: Override is still present | |
| 9 | Run an individual branch in the MBP project | Branch should run with Global default of MIDDLE | Fail: Job runs in PERF |
