-
Improvement
-
Resolution: Not A Defect
-
Major
-
None
The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps.
e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view.
sh cmd:"npm install", name: "npm"
- duplicates
-
JENKINS-26107 Allow stage to operate as a labelled block
-
- Closed
-
-
JENKINS-37324 We would like a more meaningful description of a step
-
- Closed
-
[JENKINS-36933] Name or alias Shell Script Step (sh)
| Summary | Original: Name or alias sh Steps | New: Name or alias Shell Script Step (sh) |
| Description |
Original:
The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps. e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. `sh cmd:"npm install", name: "npm"` |
New:
The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps. e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. {code:java} sh cmd:"npm install", name: "npm" {code} |
| Description |
Original:
The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps. e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. {code:java} sh cmd:"npm install", name: "npm" {code} |
New:
The `sh` step adds a "Shell Script" step in the Pipeline. However, there could be multiple such steps including steps from various plugins (e.g., Docker), which makes it hard to distinguish the steps. We should perhaps add an optional parameter to sh to specify a name or alias which would then appear in the pipeline steps. e.g., the following can be the step for npm which would show as "Shell script: npm" in the pipeline view. {code:java} sh cmd:"npm install", name: "npm" {code} |
| Workflow | Original: JNJira [ 173688 ] | New: JNJira + In-Review [ 185285 ] |
| Component/s | New: workflow-plugin [ 18820 ] | |
| Component/s | Original: build-pipeline-plugin [ 15962 ] |
| Component/s | New: pipeline-general [ 21692 ] |
| Component/s | Original: workflow-plugin [ 18820 ] |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Attachment | New: Screen Shot 2016-10-03 at 4.13.46 PM.png [ 34228 ] |
