Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
3.1
-
Severity 3 - Minor
-
Description
When trying to run a Mercurial build on OSX, I'm getting the following error message via the Bamboo UI despite the fact that the Mercurial capability seems to be set correctly:
Error encountered while triggering manual build: Mercurial not found. Is Mercurial Executable capability properly set in configuration?
Plan 'DEMO-IDE' did not start
When looking at the logs, the error seems to be related to some Mercurial libraries that can not be found:
Caused by: com.atlassian.bamboo.plugins.hg.HgCommandException: command [/usr/local/bin/hg, version, --config, ui.ssh=ssh -o StrictHostKeyChecking=no -o BatchMode=yes] failed. Working directory was `/Users/jens/src/bamboo/trunk/bamboo-homes/8085/xml-data/build-dir'. stderr: abort: couldn't find mercurial libraries in [/usr/platlib/Library/Python/2.6/site-packages /usr/local/bin /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC /Library/Python/2.7/site-packages] (check your install and PYTHONPATH) stdout: at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.runCommand(HgCommandProcessor.java:376) at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.checkHgExistenceInSystem(HgCommandProcessor.java:86) ... 176 more Caused by: com.atlassian.utils.process.ProcessException: Non-zero exit code: 255 at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:83) at com.atlassian.utils.process.ExternalProcess.finish(ExternalProcess.java:330) at com.atlassian.utils.process.ExternalProcess.execute(ExternalProcess.java:373) at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.runCommand(HgCommandProcessor.java:371) ... 177 more
Actions required
- We should let the user know what's actually wrong so he/she can fix it.
- I don't have the issue when running hg via the command line... is there an actual bug here?