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

Add skip conditions to control the flow of Bamboo Stage execution

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Stages
    • 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.

      This feature will allow skipping any Stage of a Plan during execution Based on a condition. For example, when configuring a skip condition on a Stage, users can have something like these: "If the branch name is 'test_branch', skip this Stage", "If it's 9am to 6pm now, skip this Stage", "If the Plan is triggered manually, skip this Task".

      Skip this Stage based on:

      1. time interval
      2. how the Plan (and therefore the Stage) has been triggered
      3. who triggered the Plan/Stage (list of user names or groups)
      4. who committed changes to the Configured Repositories for this Plan(Stage)
      5. what branch is running the Stage (the user can specify a list of branch names, or set a regular expression)
      6. the Agent or Environment (user can specify the agent name)

      (This list can be expanded)

            [BAM-13321] Add skip conditions to control the flow of Bamboo Stage execution

            Vitali Vikhliayeu added a comment - - edited

            I vote as well.

            Colleagues, maybe for anyone it will be useful:

            You could try to use the "Stop job execution" as the first task of the jobs.

            With some conditions for these tasks, you could control the flow of execution.

            Vitali Vikhliayeu added a comment - - edited I vote as well. Colleagues, maybe for anyone it will be useful: You could try to use the " Stop job execution " as the first task of the jobs. With some conditions for these tasks, you could control the flow of execution.

            sta-szek added a comment -

            i vote as well

            sta-szek added a comment - i vote as well

             I would vote for this feature if I could

            Phil Rittenhouse added a comment -  I would vote for this feature if I could

            Dawei Wang added a comment -

            Boo too. Why not implement this.

            Dawei Wang added a comment - Boo too. Why not implement this.

            Boo. Even 40-year old "make" has this functionality. It's crazy for small changes to take hours to produce an artifact. Bamboo is not a very agile tool, is it? It's an unwieldy sledgehammer forged from the pain of Java developers.

            Mike Eldridge added a comment - Boo. Even 40-year old "make" has this functionality. It's crazy for small changes to take hours to produce an artifact. Bamboo is not a very agile tool, is it? It's an unwieldy sledgehammer forged from the pain of Java developers.

            We've decided not to introduce any skipping functionality into Bamboo stages.

            James Dumay added a comment - We've decided not to introduce any skipping functionality into Bamboo stages.

            ArmenA added a comment - - edited

            ArmenA added a comment - - edited This might combine some other feature requests: https://jira.atlassian.com/browse/BAM-11104 https://jira.atlassian.com/browse/BAM-10443 https://jira.atlassian.com/browse/BAM-8789 https://jira.atlassian.com/browse/BAM-11257

              Unassigned Unassigned
              akhachatryan ArmenA
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: