-
Bug
-
Resolution: Fixed
-
Minor
-
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 a few hours 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 a few hours ago - Google Chrome Version 63.0.3239.108 (Official Build) (64-bit)
Summary:
The inline help for Speed/Durability Settings for Multibranch Pipeline jobs isn't being shown on the Configure page. It can still be viewed in the global Manage Jenkins --> Configure System page.
Steps to recreate:
1. Have an existing MBP project. In my case, this is on a Bitbucket server, and has several branches on it. Note that before I observed this issue, I was using the previous betas, and had made several changes to the durability setting. So, this is not a brand-new MBP project.
2. As a user with the correct amount of permissions, go to the job's Configure page.
3. Under Behaviors --> Property Strategy, find Pipeline Speed/Durability Override. Look for the little icons to the right hand side of the screen - they are not there.
4. Go back to the main Manage Jenkins page, and select Configure System. Here, the inline help for Pipeline Speed/Durability Settings is present:
I've taken a guess at which plugin this issue belongs to.