Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bitbucket pipeline not start automatically after on push on a configured branch

Dear Bitbucket Support,

We really enjoy the pipeline CI, but our issue is that we need to manually start the pipeline for each bitbucket remote push on dev.

Is it really the case or how we can configure to auto start after each commit push on a remote dev branch?

Sample YML config:

image: node:11.8.0

yarncache: /usr/local/share/.cache/yarn/v1

- step: &install
name: Install
- node
- yarncache
- yarn

- step: *install

I looking forward to hearing from you as it will be really useful to have auto start on remote push. We do not have any pipeline related webhook in bitbucket cloud. 

Best Regards,
Attila Csanyi

7 answers

Dear @Attila Csanyi ,
currently I'm configuring a custom pipeline as you were when this post was created and actually I'm facing the same problem.

Just in case, did you find some useful solution to trigger automatically a custom pipeline? If so, how could I achieve that?

Thank you so much in advance for your your time.
Best regards,


After testing for a while I got to make the automatic pipeline just by removing the "custom:" tag on my bitbucket-pipelines.yml file. Leaving it, in my case, as follows:

- step:

Thank you so much anyway, cheers.

This worked for me! Thank you Kiko_BZ

Hi @Attila Csanyi

As discussed,  custom pipelines do not run automatically on a commit to a branch.

Any help is appreciated, thx.

Dear @Venugopala Naidu ,

Thanks for the detailed answer. It seems we need exactly the opposite behaviour: auto started pipeline for only the custom branches as behind those branches we have environment like dev, staging or prod and would be great to avoid manual interaction and just start pipeline which test, build and deploy to the relevant environment as soon as a push happened.

So if we need auto start pipeline for our dev or master branches, we basically need a custom pipeline which cover all branches except dev or master, is there any way to achieve this in bitbucket-pipelines.yml?

Thanks for your help,

Attila Csanyi

Dear @Venugopala Naidu ,

Thanks for the quick reply. We read relevant documentation, but it seems still not clear. Do you mean because I have custom pipeline for dev (considered as

custom: # Pipelines that can only be triggered manually

) so thats why it cannot run automatically?

Do we need to use `default` pipeline instead, can you help me and suggest how the above valid config can trigger pipeline in each remote dev push?

We never able to trigger that pipeline with a push.

Thanks for the more detailed help.

Best Regards,
Attila Csanyi

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events