This question is in reference to Atlassian Documentation: Polling the repository for changes
I have a linked repository configured with the "master" branch selected, and a plan trigger to poll for repository changes. The problem is that even though the master branch is selected, a push to any branch triggers a build, which in this case creates a loop because my deployment plan (which is automatically triggered on successful build) pushes to the branch corresponding to the environment (triggering another build).
Why doesn't the selected branch have an effect on repository polling? and how can this situation be remedied?
Thank you.
Hello Aaron,
Thank you for you inquire.
If you do not want to have the triggering (polling) available to the reminder branches, please go to each of the branches under "Branches >> [your branch] >> Branch details" tab and under "Trigger type >> Change trigger" select Manual.
image2016-3-8 17:17:41.png
Every branch created takes as default the configuration you have under "Plan configuration", so if you have polling as trigger method under "Plan configuration >> Triggers" tab all the branches created will behave no different.
If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.
Thank you for your understanding.
—
Kind regards,
Rafael P. Sperafico
Atlassian Support
Hi Rafael,
Thanks for your response.
I'm not actually using branch plans. I am hoping I don't need to do that, as I understand that each branch plan counts toward the 10 plan limit in our subscription. I just have the main plan, but the default repository is set up to track the "master" branch, so I only want the "master" branch to trigger the main plan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.