• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Deployments, Triggers
    • None
    • 1
    • 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.

      Allow the triggering of deployments to be represented as a stage in a singe plan so that deployments are visible in a single pipeline view.

            [BAM-13347] Represent deployment triggers as stages within a plan

            FWIW:

            • "after successful stage" trigger is coming to Bamboo 5.10
            • "deployment environment after previous successful deployment" trigger is available since 5.8

            Marcin Gardias added a comment - FWIW: "after successful stage" trigger is coming to Bamboo 5.10 "deployment environment after previous successful deployment" trigger is available since 5.8

            Can someone from Atlassian give us an update or ETA on this issue, please?

            Pablo Garcia added a comment - Can someone from Atlassian give us an update or ETA on this issue, please?

            We're reviewing our usage of the tool right now, until the REST API is improved and you can run tests against a deploy it's useless

            Deleted Account (Inactive) added a comment - We're reviewing our usage of the tool right now, until the REST API is improved and you can run tests against a deploy it's useless

            We quit waiting and moved away from Bamboo as our CICD tool. It's to bad too because for the most part its a good product. They just don't seem to care what people actually need in the product...

            Jason Kirton (Inactive) added a comment - We quit waiting and moved away from Bamboo as our CICD tool. It's to bad too because for the most part its a good product. They just don't seem to care what people actually need in the product...

            I'm starting to think if I should stop waiting for this feature and move on.

            Martijn van der Kamp added a comment - I'm starting to think if I should stop waiting for this feature and move on.

            Neil Hunt added a comment -

            Including deployments as merely steps in an overall "delivery plan" seems fundamental to calling Bamboo a continuous delivery tool. It has so many features that GoCD, CodePipeline, Jenkins Workflow don't have, but they all seem to embrace the principals of continuous delivery more so than Bamboo does because of this missing feature.

            There are workarounds, but even a simple trigger for a deployment environment of a previous successful deployment would go a long way and I can't see how that is too difficult to add..

            Neil Hunt added a comment - Including deployments as merely steps in an overall "delivery plan" seems fundamental to calling Bamboo a continuous delivery tool. It has so many features that GoCD, CodePipeline, Jenkins Workflow don't have, but they all seem to embrace the principals of continuous delivery more so than Bamboo does because of this missing feature. There are workarounds, but even a simple trigger for a deployment environment of a previous successful deployment would go a long way and I can't see how that is too difficult to add..

            It's hard to continue to be supportful of Bamboo when it seems to have low priority for so many fundamental pipeline related features. Created June 2013?? killing me smalls..

            Matthew Grose added a comment - It's hard to continue to be supportful of Bamboo when it seems to have low priority for so many fundamental pipeline related features. Created June 2013?? killing me smalls..

            Mark Brown added a comment -

            Any further update as to when this feature might be implemented? It seems so fundamental to be able to effectively use Bamboo deployment plan that this ought to be a no brainer.

            How else can you have an automated deployment pipeline across multiple environments, each with a different set of tests being automatically executed.

            It should be possible to trigger a deployment plan as a stage or job within a build plan in order to achieve this.

            Mark Brown added a comment - Any further update as to when this feature might be implemented? It seems so fundamental to be able to effectively use Bamboo deployment plan that this ought to be a no brainer. How else can you have an automated deployment pipeline across multiple environments, each with a different set of tests being automatically executed. It should be possible to trigger a deployment plan as a stage or job within a build plan in order to achieve this.

            This would be a great functionnality. We proceed like this:

            • Within the same Environement, let's say Production, we switch offline one server and deploy to verify before switching it online and then deploy to all servers.
            • Those tasks have to be staged with the possibility to run manually some of them.

            Salah Khamassi added a comment - This would be a great functionnality. We proceed like this: Within the same Environement, let's say Production, we switch offline one server and deploy to verify before switching it online and then deploy to all servers. Those tasks have to be staged with the possibility to run manually some of them.

            Any update on this issue?

            Deleted Account (Inactive) added a comment - Any update on this issue?

              Unassigned Unassigned
              jdumay James Dumay
              Votes:
              67 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 16m
                  16m