We occasionally get an "Unable to detect changes" error, but the build seems to work. More specifically:
Unable to detect changes
(com.atlassian.bamboo.plugins.hg.HgCommandException : command /usr/bin/hg id -i --debug -rev feature/[name of the build]
It seems to be caused by:
stderr: abort: HTTP Error 500: Internal Server Error stdout:using [our hg server] sending capabilities command sending lookup command
Has anyone experienced this and what is the cause/resolution
That was me, i withdrew the comment because i see that it's actually the hg binary that returns the error. My question was if it was a new buildserver where the hg binary was deployed and configured through the interface. If any other HG checkouts works at this point, this can't be the issue.
You don't happen to see anything else in the bamboo logs?
It wouldn't let me ad another comment yesterday.
This has been happening for a long time (I don't remember exactly when), and I don't see anything in the logs that appear to be related. The builds work. My feeling is that maybe this is more of a network or timeout issue between the servers, since mercurial is on a different server than bamboo. One of the developers keeps asking, so I thought I'd post it here to see if anyone had experienced this or knew of possible solutions.
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...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot