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

Add a RETRY on failure option for the atlassian/trigger-pipeline pipe

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • Pipelines - Pipes
    • None
    • 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

      Problem Definition

      If the WAIT variable of the atlassian/trigger-pipeline pipe is set to true, the pipe will wait for the triggered pipeline to complete. If the triggered pipeline fails, this pipe will also fail.

      Sometimes that error with the triggered pipeline is not a real build failure, but it could be a network issue pulling an artifact or an image, a timeout making an internet call, a failure in the Atlassian pipeline runner, etc. In these cases, rerunning the triggered pipeline may solve the issue.

      Right now, users need to manually rerun the failed step that includes the pipe command.

      Suggested Solution

      It has been requested to add a RETRY on failure option for the atlassian/trigger-pipeline pipe, so that if the triggered pipeline fails, a new one gets triggered without the user needing to rerun manually the failed step.

      The number of times that the triggered pipeline runs (in case of failure) could also be configurable.

      Workaround

      Users can manually rerun the failed step that includes the pipe command.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tboudale Theodora Boudale
            Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: