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

Make a stage or multiple stages exclusive and atomic so it will not run in parallel with other revisions

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Builds
    • 0
    • 2
    • 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.

      It would be nice to set an 'exclusive' checkbox for a stage so it doesn't run multiple times at once.

      revision a compile b run unit tests c deploy to int d run integration tests
      4 running      
      3 running      
      2 done done awaiting rev 1 to finish stage c and d  
      1 done done done running

      While stages a and b can run in parallel, c and d can only run one revision at a time. In order to avoid collisions when deploying and running tests on the integration environment.

            [BAM-11052] Make a stage or multiple stages exclusive and atomic so it will not run in parallel with other revisions

            Atlassian Update – [12 April 2019]

            Hi everyone,

            Thank you for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future.

            We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:

            1. Performance and stability improvements
            2. Providing building blocks for High Availability and Disaster Recovery solutions
            3. Improving permission system
            4. Allowing per-project allocation of resources
            5. Improving Bitbucket Server and Jira integrations

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Bamboo Team

            Krystian Brazulewicz added a comment - Atlassian Update – [12 April 2019] Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including: Performance and stability improvements Providing building blocks for High Availability and Disaster Recovery solutions Improving permission system Allowing per-project allocation of resources Improving Bitbucket Server and Jira integrations We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Bamboo Team

            Implementing BAM-11048 would allow for stage c and d to be merged. Which would lessen the need for making multiple consecutive stages exclusive; exclusivity for one stage would be enough, which should be much easier to implement.

            Jorrit Salverda added a comment - Implementing BAM-11048 would allow for stage c and d to be merged. Which would lessen the need for making multiple consecutive stages exclusive; exclusivity for one stage would be enough, which should be much easier to implement.

              Unassigned Unassigned
              akhachatryan ArmenA
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: