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-16028

Child plan should not run if it does not have a branch plan that matches the parent

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

      Bamboo will currently run a child plan whenever the parent plan completes, regardless if the child has a branch plan configured for the branch the parent just finished.

      In order to support having a "master" plan that then has many children that do different things depending on the branch name, Bamboo should have an option to respect the child plan branches.

      This has come up because we have multiple platforms to QA on, but only need to run those QA jobs on some subset of parent plan builds which can be identified by the branch name. E.g. that branches containing the string "project1" in their name should trigger child1 after building, and branches containing the string "project2" should trigger child2.

            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-16028

            Child plan should not run if it does not have a branch plan that matches the parent

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

                Bamboo will currently run a child plan whenever the parent plan completes, regardless if the child has a branch plan configured for the branch the parent just finished.

                In order to support having a "master" plan that then has many children that do different things depending on the branch name, Bamboo should have an option to respect the child plan branches.

                This has come up because we have multiple platforms to QA on, but only need to run those QA jobs on some subset of parent plan builds which can be identified by the branch name. E.g. that branches containing the string "project1" in their name should trigger child1 after building, and branches containing the string "project2" should trigger child2.

                        Unassigned Unassigned
                        f4787cf404c1 Matt Walker
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            f4787cf404c1 Matt Walker
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated: