We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-15067

dependency blocking strategy should work independent of polling mechanism

    • 0
    • 1
    • 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.

      Suppose, there are two build plans A and B.
      B is dependent on A (this dependency has been configured in the build plan A). So, A is parent and B is child.
      Now the scenario is -
      Build plan A is triggered - first
      Build plan B is triggered manually when plan A is running - second
      Now, both A and B are running.
      Scenario, dependent build B(from build plan A) is not getting triggered after completion of manually triggered build B.
      Ideally, dependent build B should wait in queue and should get triggered automatically after the completion of manually triggered build.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-15067

            dependency blocking strategy should work independent of polling mechanism

              • 0
              • 1
              • 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.

                Suppose, there are two build plans A and B.
                B is dependent on A (this dependency has been configured in the build plan A). So, A is parent and B is child.
                Now the scenario is -
                Build plan A is triggered - first
                Build plan B is triggered manually when plan A is running - second
                Now, both A and B are running.
                Scenario, dependent build B(from build plan A) is not getting triggered after completion of manually triggered build B.
                Ideally, dependent build B should wait in queue and should get triggered automatically after the completion of manually triggered build.

                        Unassigned Unassigned
                        22dcdf0c9c0f Rahul
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            22dcdf0c9c0f Rahul
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: