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

    • Icon: Suggestion 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.

      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.

            [BCLOUD-22872] Add a RETRY on failure option for the atlassian/trigger-pipeline pipe

            Thanh Truong added a comment -

            +1

            Thanh Truong added a comment - +1

            Tiago Jesus added a comment -

            +1

            Tiago Jesus added a comment - +1

            Dhiogo Boza added a comment -

            +1

            Dhiogo Boza added a comment - +1

            Daniel Pardo added a comment -

            Is there some movement on this? it would be very useful to have this implemented.

            Daniel Pardo added a comment - Is there some movement on this? it would be very useful to have this implemented.

            Tamas Virag added a comment -

            +1

            Tamas Virag added a comment - +1

            Jay Seletz added a comment -

            To follow up on my prior comment, just to clarify, it appears the PR I referenced only retries when the pipe experiences an API call failure.  This request is to enable retries when the triggered pipeline itself fails.

            Jay Seletz added a comment - To follow up on my prior comment, just to clarify, it appears the PR I referenced only retries when the pipe experiences an API call failure.  This request is to enable retries when the triggered pipeline itself fails.

            Jay Seletz added a comment -

            Also please see my reply on this thread: https://community.atlassian.com/t5/Bitbucket-questions/Can-you-add-a-retry-on-failure-option-for-the-trigger-pipeline/qaq-p/2467873#U2600230

            Jay Seletz added a comment - Also please see my reply on this thread: https://community.atlassian.com/t5/Bitbucket-questions/Can-you-add-a-retry-on-failure-option-for-the-trigger-pipeline/qaq-p/2467873#U2600230

            Jay Seletz added a comment -

            Hi - I see this PR is merged, when is this feature going to be release?  https://bitbucket.org/atlassian/trigger-pipeline/pull-requests/46

            Jay Seletz added a comment - Hi - I see this PR is merged, when is this feature going to be release?   https://bitbucket.org/atlassian/trigger-pipeline/pull-requests/46

            Viktor Gogulenko added a comment -

            It would be really helpful for us as we are trying to achieve zero-manual work with pipelines and sometimes they are failing just because there was a network issue while connect to npm registry, step is failing and it blocks the whole development pipeline as we need to relaunch it manually. Thanks!

            Viktor Gogulenko added a comment - It would be really helpful for us as we are trying to achieve zero-manual work with pipelines and sometimes they are failing just because there was a network issue while connect to npm registry, step is failing and it blocks the whole development pipeline as we need to relaunch it manually. Thanks!

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

                Created:
                Updated: