Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55254

Customize mappings from Jenkins Results to Bitbucket State

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Jenkins 2.150.1 LTS
      bitbucket-branch-source-plugin 2.2.16
    • 930.ve6a_885b_3558f

      A recent change done in JENKINS-49640 is causing an issue with our workflow.

      In our builds, we use the NOT_BUILT option to mark builds that we chose not to build, not due to them not being needed, but due to the user not requesting them, erroneous triggers, etc.

      The change performed in JENKINS-49640 broke this workflow.

      We suggest adding custom mappings from Jenkins Results to BB build states, configurable in UI.

          [JENKINS-55254] Customize mappings from Jenkins Results to Bitbucket State

          Nikolas Falco added a comment -

          It is already possible map the build status to the build notification result within limits, you can not map FAILED build to SUCESS, in this case disable build notification and use a bitbucket-build-status-notifier from the pipeline for custom mapping.

          Nikolas Falco added a comment - It is already possible map the build status to the build notification result within limits, you can not map FAILED build to SUCESS, in this case disable build notification and use a bitbucket-build-status-notifier from the pipeline for custom mapping.

            hellspam Roy Arnon
            hellspam Roy Arnon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: