Details
-
Type:
Task
-
Status: To Do (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: content
-
Labels:None
-
Similar Issues:
Description
Most of the time when people use currentBuild.result, they really want the behavior from currentBuild.currentResult or currentbuild.resultIsBettterOrEqualTo/currentbuild.resultIsWorseOrEqualTo (see linked issues).
Review the existing documentation and update to use these new methods.
Attachments
Issue Links
- relates to
-
JENKINS-46325 Should we use result or currentResult?
-
- Open
-
-
JENKINS-41275 Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)
-
- Closed
-
-
JENKINS-42521 RunWrapper should have a "getCurrentResult()" method
-
- Closed
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Link |
This issue relates to |
Remote Link | This issue links to "PR-31 (Web Link)" [ 17101 ] |
Summary | Update "currentBuild.result" docs and examples to use currentBuilt.currentResult and resultIsBetter/IsWorse | Basic credentials are only supported over HTTPS secured connections |
Summary | Basic credentials are only supported over HTTPS secured connections | Update "currentBuild.result" docs and examples to use currentBuilt.currentResult and resultIsBetter/IsWorse |
Rank | Ranked higher |
Description |
See linked issues. Most of the time when people use {{currentBuild.result}}, they really want the behavior from {{currentBuild.currentResult}} or {{currentbuild.resultIsBettterOrEqualTo}}/{{currentbuild.resultIsWorseOrEqualTo}}. Review the existing documentation and update to use these new methods. |
Most of the time when people use {{currentBuild.result}}, they really want the behavior from {{currentBuild.currentResult}} or {{currentbuild.resultIsBettterOrEqualTo}}/{{currentbuild.resultIsWorseOrEqualTo}} (see linked issues). Review the existing documentation and update to use these new methods. |
Link | This issue relates to JENKINS-46325 [ JENKINS-46325 ] |