Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-364

Update "currentBuild.result" docs and examples to use currentBuilt.currentResult and resultIsBetter/IsWorse

    XMLWordPrintable

    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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-46325 Should we use result or currentResult?

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-41275 Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-42521 RunWrapper should have a "getCurrentResult()" method

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link PR-31

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bitwiseman Liam Newman
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: