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 have a bunch of build plans with "Create plan branch for new branches" selected under the branch tab of the "Plan configuration" section of the build plan.
I notice that on initial creation of the plan branch, the build plan runs for that branch even if the repository change detection file pattern is excluding a commit from that directory in GIT.
For example, if I commit into this dir:
/source/app/a
but my project's build plan has this file detection pattern:
^/source/app/b/*
Creating a new branch on "source" but committing only into "a" still triggers a build.
Does anyone know how to avoid this? I would only like build plans to run if I commit into directories that they are watching.
Thanks.
Hi Salmaan,
Yes, you are right. I believe it is a known bug as described here - Branch builds do not honor Linked Repos includes/excludes on branch creation that has not been fixed yet.
Thanks,
Robhit
Thanks @robhit - the link to Branch builds do not honor Linked Repos includes/excludes on branch creation (BAM-15899) is defunct, so here it is again ;)
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.