This question is in reference to Atlassian Documentation: Configure bitbucket-pipelines.yml
We'd like to be able to start a pipeline by using a specific tag on a branch. Our setup has 6 environments, production, staging, int-a, dev-a, int-b and dev-b. We are using a custom git-flow workflow with master, develop, feature/*, defect/*, release/* and hotfix/* branches. We'd like to direct the same release/* branch to start two different pipelines, depending upon a git tag. By default, the release/* branch would trigger a build and deploy to int-a, but once we're happy with this at some point in the future, we could trigger a build and deploy for this release branch to int-b using the tag. So, always trigger the build and deploy to int-a, and only build and deploy to int-b when a specific tag or tag pattern is added to the branch.
I know we could just use two different branches, but extending for the tag would be grand.
If you have it, bonus, how do I do that then?
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