Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-18519

Optional step for pipeline that never blocks PR to get merge, even when fails

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      There should be an option for a step to be non-critical for it to not block PRs from being merged.

      Use case :

      When merge checks are set to block PR if any step fails, one step does a network call to npm and fails for some reason, but the step actually is not at all related to the code. It shows the status of the project from npm so cannot be shifted to after-script of a step as the status for the whole pipeline should be fail. Since this step is wanted to have an automatic trigger so cannot be a custom step.

      Whats needed:

      • A step which doesn't block PR for being merged when fails
      • Shows pipeline status as fail if step failed
      • Configurable through bitbucket-pipelines.yml

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            shashwat.dixit Shashwat Dixit
            Votes:
            18 Vote for this issue
            Watchers:
            13 Start watching this issue

              Dates

              Created:
              Updated: