-
Suggestion
-
Resolution: Unresolved
-
None
The stages feature in Bitbucket pipelines does not allow manual triggers for a step in a stage at the moment as mentioned in the limitations section
A stage can't contain manually triggered steps, but you can configure a stage to be manually triggered.
The request is to allow the manual triggers for a step in a stage.
Be aware that there are several consciences of having manual triggers inside a stage:
- Partially completed deployment stages can't be continued if another change was subsequently deployed to the same environment. It means that a manual step inside a stage can't be triggered if another pipeline is deployed to the same environment.
- On a stage redeploy manual steps won't be taken into account.
[BCLOUD-22223] Support manual trigger for a step in a stage
badacfdb410f how do dynamic pipelines solve this missing feature? Can you link some documentation about it?
If that help, you should be able to solve most of those problems with Dynamic Pipelines. But that requires Premium
+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.
Another year waiting for this... you're testing my patience big time!
I would use this as a workaround for not being able to reference same deployment environment in multiple stages, I could then bundle all steps into a single stage, and use manual trigger for the steps I need, instead of a stage.
Any chance for an update on this request? Having a manual approval for applying our Terraform plans is a strongly desired feature at our company.
Is there a status update on this issue? There has been no Atlassian Employee activity since July 18th, 2023.
As others have mentioned, a manual trigger on the entire stage really defeats the purpose of having a manual trigger altogether. It leaves the pipeline operators blind to what changes are actually going to be made by the steps in that stage. I can't in good confidence "Deploy" the stage that both plans the changes and applies them.
f9c8253b49c3
I wrote an article on this.
https://medium.com/@jedfra6/how-i-finally-solved-cicd-in-bitbucket-after-2-years-of-trying-080e2159a798
Since that time I also solved an issue with admin checks for specific jobs, which is great.
Would I prefer to have all that ootb in Bitbucket - for sure. But I'm happy at least I have tools at hand to help me go forward