Mercurial operations fail due to mis-configured HG capability

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Mercurial builds fail with the following error:

"java.lang.RuntimeException : com.atlassian.bamboo.repository.RepositoryException: Mercurial Executable capability `/usr/local/bin/hg' does not seem to be a hg client. Is it properly set?"
but executable exists and works properly.
Some experimants shows that bamboo calls hg with illegal arguments:
version --config ui.ssh=ssh -o StrictHostKeyChecking=no -o BatchMode=yes
hg reports:
hg version: option -o not recognized
---------------------
java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: Mercurial Executable capability `/usr/local/bin/hg' does not seem to be a hg client. Is it properly set?
	at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:119)
	at com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:79)

Caused by: com.atlassian.bamboo.repository.RepositoryException: Mercurial Executable capability `/usr/local/bin/hg' does not seem to be a hg client. Is it properly set?
	at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.checkHgExistenceInSystem(HgCommandProcessor.java:91)
	at com.atlassian.bamboo.plugins.hg.HgRepositoryAccessImpl.<init>(HgRepositoryAccessImpl.java:82)

Cause

The Mercurial capability is pointed to an incorrect location.

Resolution

 Ensure that the configured Mercurial Capability points to the correct hg executable.

 

 

 

 

 

 

Last modified on Jun 27, 2013

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.