You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am trying to use bitbucket-pipelines to test and in a separate step deploy,
When a pull-request is created I want to run unit tests. I see that I can do this with the pull-requests feature.
When the code is merged, I want to create a zip and deploy (copy) code to s3
How do I trigger a step when the code is merged? Not when the pull-request is created.
Do I need to use tags?
Hello Joseph,
For the workflow you're mentioning, you can use branch pipelines.
For example:
pipelines:
branches:
master:
- step:
script:
- # Create zip and deploy to s3.
pull-requests:
feature-branch-*:
- step:
script:
- # Run unit tests
In this configuration, the zip creation and deployment will only happen when a new commit is introduced to the master branch. i.e. Whenever a feature branch is merged to master.
It is possible to use tags. But that doesn't sound like it's a part of your current workflow, so it isn't necessary to introduce if you don't need them.
Does that work for you?
Thanks,
Phil
@Philip Hodder The branch pipeline on `master` isn't really a solution for us, because we can't just run the pipeline willy-nilly on any commit to `master`; we need to know something about how that commit originated. Consider:
When a PR from a `release/*` branch is merged into `master`, I would like to run an action that:
I can't hook this action to any commit to `master`, because a hotfix could come in that gets deployed to `master`, and I wouldn't want that change to trigger the release branch-related workflow.
Any suggestions?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Max DeCurtins I am looking to do a flow similar to the one described by you. Did you find any solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.