• 13
    • 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.

      The stages feature in Bitbucket pipelines does not allow parallel steps in a stage at the moment as mentioned on the limitations section

      A stage can't include parallel steps.

       
      The request is to allow the parallelization of steps in a stage for faster builds.

            [BCLOUD-22214] Support parallel steps in stages

            +1 for using parallel steps within stages, please implement this.

            Phong Khưu added a comment - +1 for using parallel steps within stages, please implement this.

            Euclecio Rodrigues added a comment - - edited

            +1 Bitbucket Pipelines need this feature so much, how to run steps in parallel using the same environments variables? It's impossible

            Euclecio Rodrigues added a comment - - edited +1 Bitbucket Pipelines need this feature so much, how to run steps in parallel using the same environments variables? It's impossible

            +1 much needed. Honestly I don't understand how this is not implemented yet. The issue has been raised two and a half years ago. People who are proficient with other pipeline solutions will really miss this feature. Hopefully this gets resolved soon.

            Lennert Mertens added a comment - +1 much needed. Honestly I don't understand how this is not implemented yet. The issue has been raised two and a half years ago. People who are proficient with other pipeline solutions will really miss this feature. Hopefully this gets resolved soon.

            This is a much needed capability. Please implement!

            Brian Murnock added a comment - This is a much needed capability. Please implement!

            +1
            it will be helpful to develop flexible pipelines

            Rustam Khanafeev added a comment - +1 it will be helpful to develop flexible pipelines

            +1

            Amazing how many basic features which are staples of CI/CD development are just not allowed, or a limitation, or totally impossible in Bitbucket pipelines. Do Atlassian realise that their main competititors in this space i.e. GitHub/GitLab are totally blowing Bitbucket pipelines in the middle of last decade. This ticket and dozen or so other tickets to allow for basic stuff, like variablising deployment variables, allowing conditional steps, deployments with parallel steps, more than one step with a deployment in a stage and other very simple capabilities to implement is really hindering the ability for engineers to use Bitbucket pipelines properly. These tickets have been open for literally years, with no updates, no comments from anyone at Atlassian and it's very poor.

            Adam Sambridge added a comment - +1 Amazing how many basic features which are staples of CI/CD development are just not allowed, or a limitation, or totally impossible in Bitbucket pipelines. Do Atlassian realise that their main competititors in this space i.e. GitHub/GitLab are totally blowing Bitbucket pipelines in the middle of last decade. This ticket and dozen or so other tickets to allow for basic stuff, like variablising deployment variables, allowing conditional steps, deployments with parallel steps, more than one step with a deployment in a stage and other very simple capabilities to implement is really hindering the ability for engineers to use Bitbucket pipelines properly. These tickets have been open for literally years, with no updates, no comments from anyone at Atlassian and it's very poor.

            Kyle Baley added a comment -

            We're interested in this feature or some advice on a workaround. Our build creates four docker images (in parallel) that work in tandem and uploads them to a registry. I'd like to group these into a single stage.

            Kyle Baley added a comment - We're interested in this feature or some advice on a workaround. Our build creates four docker images (in parallel) that work in tandem and uploads them to a registry. I'd like to group these into a single stage.

            Paul Jones added a comment -

            This would help us greatly, we're using stages so that we can restrict one build per deployment environment at a time.  Not being able to include our normal parallel steps increases our build time 2 fold.

            Paul Jones added a comment - This would help us greatly, we're using stages so that we can restrict one build per deployment environment at a time.  Not being able to include our normal parallel steps increases our build time 2 fold.

            +1

            Please implement this.  I cannot use the stages feature until this is implemented.  Our builds take way too long unless parallelized.  

            Ryan Kanzeg added a comment - Please implement this.  I cannot use the stages feature until this is implemented.  Our builds take way too long unless parallelized.  

              Unassigned Unassigned
              tboudale Theodora Boudale
              Votes:
              194 Vote for this issue
              Watchers:
              98 Start watching this issue

                Created:
                Updated: