-
Story
-
Resolution: Fixed
-
Minor
-
-
Blue Ocean 1.1-beta4
Example 1
node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; }
- is duplicated by
-
JENKINS-39850 Blue Ocean should respect build.displayName
-
- Resolved
-
-
JENKINS-43295 Option to populate "message" column from pipeline script
-
- Resolved
-
- is related to
-
JENKINS-45181 Description does not display line breaks
-
- Closed
-
- relates to
-
JENKINS-45719 Description for a pipeline run is not compatible and cannot be disabled
-
- Open
-
-
JENKINS-43762 BlueOcean: build and deployment identifier/description
-
- Resolved
-
[JENKINS-41769] Developer can see a description for a pipeline run
Description |
Original:
In the old ui we are using the "currentBuild.description" to set version and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? |
New:
In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? |
Description |
Original:
In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? |
New:
*Original request* In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? *Example Pipeline* {code} node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; } {code} |
Attachment | New: #660 2017-02-07 07-52-49.png [ 35780 ] |
Attachment | Original: #660 2017-02-07 07-52-49.png [ 35780 ] |
Attachment | New: run.png [ 35781 ] |
Summary | Original: Display "description" in build | New: Developer can see a description for a run |
Summary | Original: Developer can see a description for a run | New: Developer can see a user definable description for a pipeline run |
Epic Link | New: JENKINS-35750 [ 171713 ] |
Description |
Original:
*Original request* In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? *Example Pipeline* {code} node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; } {code} |
New:
*Original request* In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? *Example Pipeline* {code} node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; } {code} |
Description |
Original:
*Original request* In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? *Example Pipeline* {code} node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; } {code} |
New:
*Scope* * {{currentBuild.description}} replaces the trigger reason on the Run screen and Message column on the activity ** Overrides any other commit or trigger reason message * Escapes HTML but allows hrefs ** HREF only displayed on the Run screen ** All html including HREF excluded when shown elsewhere, such as the message column *Original request* In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? *Example Pipeline* {code} node { sh 'ping -c 5 localhost' currentBuild.description = "go to http://www.apple.com/"; } {code} |