I am attempting to set up the alpha Bitbucket Deployments feature.
I have the following in my bitbucket-pipelines.yml in the master branch, following the documentation example:
name: Deploy to test
- chmod +x deploy_staging.sh && ./deploy_staging.sh
However, when I go to the Deployments page on the project I still see the introductory text:
I am confused on how to invoke this pipeline now as before it was set up as a custom pipeline that could be manually triggered by a specific commit.
How can I properly set up this feature and invoke the pipeline with the
Thanks for any assistance.
Ok, I've figured it out.
In my bitbucket-pipelines.yml I had all three environments set under the default step. Only one deployment is allowed here.
The instructions on the Deployments page are also a bit misleading since it is implied a "test" deployment is required when this is not the case.
All three environments are present in the instructions article for setting up the deployment - https://confluence.atlassian.com/bitbucket/bitbucket-deployments-940695276.html
Which further adds to the confusion.
Is there any way to set up a choice as to which environment the current commit can be deployed to, or will we have to keep separate bitbucket-pipelines.yml in each branch?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs