-
Task
-
Resolution: Fixed
-
Blocker
-
-
frank, tethys, christmas, pannonian, iapetus, 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1
Note: This has been implemented, but what is missing is some UI work to follow the design/limit wrapping on narrow screens (backend and pipeline components are completed, including api usage).
Scope
- Pipeline API exposes step descriptions
- Descriptions for steps reflected from the pipeline API
- Update the UI of Blue Ocean to display the steps
Design
- Has Description
- Description on left, black @ 100% opacity
**Type to the right, with em dash, black @ 50% opacity (or grey color)
- Description on left, black @ 100% opacity
- Has no Description
- Type on left, black @ 100% opacity
- Use Zeplin for extact metrics https://zpl.io/1MtiWN
Notes
We want to provide the developer a more meaningful description of the steps in Blue Ocean.
For example, if we have a shell script being executed we'd like to provide the command as the description of that step. If we don't have that information, we'd like to fall back to a description of the step otherwise fall back to the step name.
- blocks
-
JENKINS-35864 Step section in log sticks to result header when scrolling
-
- Resolved
-
- duplicates
-
JENKINS-31582 Log / document the plugin usage in the flow nodes
-
- Resolved
-
- is blocked by
-
JENKINS-43934 GString kept unevaluated as long as StepDescriptor.newInstance (was: Pipeline build fails with serialization error when using string interpolation)
-
- Closed
-
- is blocking
-
JENKINS-40536 Show question answered on build approvals
-
- Open
-
- is duplicated by
-
JENKINS-42624 Custom title for build steps
-
- Reopened
-
-
JENKINS-43793 Ability to name pipeline steps
-
- Closed
-
-
JENKINS-36933 Name or alias Shell Script Step (sh)
-
- Resolved
-
-
JENKINS-39709 Use SCM extension [$class: 'ScmName'] in Pipeline step
-
- Resolved
-
-
JENKINS-41156 [Pipeline] Have shell and batch steps be renameable
-
- Resolved
-
-
JENKINS-28293 Display more information about Pipeline steps
-
- Resolved
-
-
JENKINS-43030 Naming Step sections in Blue Ocean
-
- Resolved
-
-
JENKINS-43545 Ability to name/label General Build Steps for display/reporting purpose
-
- Resolved
-
-
JENKINS-40400 Meanful comments in logs
-
- Closed
-
- is related to
-
JENKINS-44718 Step description does not show ellipsis when truncated
-
- Closed
-
- relates to
-
JENKINS-47101 Pipeline withCredentials step does not mask step descriptions for variables with the same name as existing system variables
-
- Resolved
-
-
JENKINS-44094 Hide specific steps in build view
-
- Open
-
-
JENKINS-55410 Add label attribute for persistable steps to improve usability
-
- Resolved
-
-
JENKINS-52902 Would a PR be accepted with a new "labelledShell" step, or an optional "label" argument to the "sh" step?
-
- Fixed but Unreleased
-
-
JENKINS-45101 Display meaningful summaries for metasteps
-
- Resolved
-
- links to
thclpr - I was thinking maybe we could add label support for other common steps as well. That's why I named the plugin labelled-steps instead of labelled-shell-step
I don't know if it's going to be feasible / easy to support other steps, but it's worth a shot (sh step was thankfully trivial to modify). Hopefully at some point Jenkins core will support custom labels for any step.