Mercurial operations fail due to mis-configured HG capability
症状
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)
原因
The Mercurial capability is pointed to an incorrect location.
ソリューション
Ensure that the configured Mercurial Capability points to the correct hg executable.
最終更新日 2013 年 6 月 27 日
Powered by Confluence and Scroll Viewport.