Why do commits from separate branches in Mercurial show up as "M" for each build?

We are using Mercurial as our source repository, and each build shows changes from other branches as "M", meaning that they were supposedly merged into the current branch, but they weren't. Changes that were never merged into the current branch are still showing up as changes made to the current branch.

Also, in some cases, commits from other branches will even kick off builds for the current branch. 

How can we get around this issue?

screenshot.png

1 answer

0 vote

Do you mean you're seeing changes from unrelated branches showing up in your branch commit list?

Please submit a support ticket via support.atlassian.com. Make sure you mention your Mercurial version and OS in the ticket.

Yes, unrelated branches, other branches, any way you want to put it. I'll create a support ticket for this.

 

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,096 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot