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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,186
Community Members
 
Community Events
176
Community Groups

Projects built on branches when not change-detection-configured code changes

We have a repo of many projects. To get around the issue of building all of our bamboo projects on each commit, under Plan Configuration > Repositories we configured our repository's Change detection options to Include only changes that matches the following pattern to the regex ^mycompany\.myproject\/*

This should now only build projects when code changes are applied to mycompany.myproject/ directory which seems to work for our master branch.

Under Plan Configuration > Branches, we set Automatic branch management to New Branches: Create plan branches for all new branches. This was so our feature branches would cause a build when the change was detected.

This should only be the case when that pattern is met but we noticed that every time we push a feature branch of code that is not in mycompany.myproject/ our bamboo projects get built. Is this a bug with the 5.x series or is this an issue with our configuration?

1 answer

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events