This question is in reference to Atlassian Documentation: Configure bitbucket-pipelines.yml
Is there a way to disable pipelines for specific branches? Or, only enable for one specific branch? We'd like to only have pipelines run on our 'master' branch for now, and ignore everything else.
Tried adding a default that simply has an echo statement in the script, but it still spends a lot of time spinning up a docker, just to do that echo. Seems like a waste of resources?
You sure can limit pipelines to run only when certain branches change.
Here's an example of a bitbucket-pipelines.yml that only runs when master is pushed
pipelines: branches: master: - step: script: - echo "only on master"
With this configuration, if I push another branch, it won't be built.
I have a single repository under bit-bucket account and this repository has this 4 branches :
- Admin - Web
I put bitbucket-pipelines.yml under master and its like that:
API: - step:
caches: - maven script: - mvn install
so I expect that when I push something to API, this will file will be triggered , but in fact it never happened, did I miss any?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot