Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20226

Blocking dependencies

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Dependencies
    • None
    • 0
    • 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

      We use Bamboo to run HITL (Hardware in the Loop) testing. In order to run the HITL plan, a commit must first pass the Systems plan. The feature I'm asking for is for a commit or branch to be blocked at the HITL plan until it passes the Systems plan.

      Conceptually it's similar to the existing dependency blocking strategy feature. The problem is the existing dependency blocking only works within the context of parent and child plans, and only blocks if the build was triggered by a parent building, not if the build was manually triggered or scheduled. I want a general way to say "Don't run this commit on plan B until it has passed plan A"

      Attachments

        Activity

          People

            Unassigned Unassigned
            45f3cebbcf3b Thomas Eliot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: