Third party plugin causes Mercurial repository configuration to get corrupted
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Saving Source Repository configuration for a Mercurial repository clears the configuration upon save, and Bamboo logs this type of errors:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
2012-03-23 10:43:27,198 INFO [1-BAM::Default
Agent::Agent:pool-5-thread-1] [DefaultErrorHandler] Recording an error:
Error occurred while executing the build for PA-PA-JOB1-1 : PA-PA-JOB1 :
command [C:\Program Files\Mercurial\hg.exe, id, -i, --debug, --rev,
default, --config, ui.ssh=ssh -o StrictHostKeyChecking=no -o
BatchMode=yes, ] failed. Working directory was `C:\Documents and
Settings\bamboo-home\xml-data\build-dir\PA-PA-JOB1'. stderr: abort:
there is no Mercurial repository here (.hg not found)
stdout:
2012-03-23
10:43:27,213 WARN [1-BAM::Default Agent::Agent:pool-5-thread-1]
[BuildAgentControllerImpl] Error occurred while executing the build for
PA-PA-JOB1-1
com.atlassian.bamboo.plugins.hg.HgCommandException:
command [C:\Program Files\Mercurial\hg.exe, id, -i, --debug, --rev,
default, --config, ui.ssh=ssh -o StrictHostKeyChecking=no -o
BatchMode=yes, ] failed. Working directory was `C:\Documents and
Settings\bamboo-home\xml-data\build-dir\PA-PA-JOB1'. stderr: abort:
there is no Mercurial repository here (.hg not found)
stdout:
at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.runCommand(HgCommandProcessor.java:358)
at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.extractTipHash(HgCommandProcessor.java:419)
at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.getRemoteTipForBranch(HgCommandProcessor.java:255)
at com.atlassian.bamboo.plugins.hg.HgRepositoryAccessImpl.getLatestRemoteRevisionHash(HgRepositoryAccessImpl.java:203)
at com.atlassian.bamboo.plugins.hg.HgRepositoryAccessImpl.retrieveSourceCode(HgRepositoryAccessImpl.java:113)
at com.atlassian.bamboo.plugins.hg.HgRepository.retrieveSourceCode(HgRepository.java:234)
at com.atlassian.bamboo.v2.build.task.CheckoutUpdateForBuild.doCall(CheckoutUpdateForBuild.java:136)
.....
Caused by: com.atlassian.utils.process.ProcessException: Non-zero exit code: -1
at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:66)
at com.atlassian.utils.process.ExternalProcess.finish(ExternalProcess.java:224)
at com.atlassian.utils.process.ExternalProcess.execute(ExternalProcess.java:267)
at com.atlassian.bamboo.plugins.hg.HgCommandProcessor.runCommand(HgCommandProcessor.java:353)
... 23 moreCause
The issue is caused due to incompatible third party plugins. If you go to Administration -> System Configuration menu of your Bamboo server, you should see a plugin for which the vendor is not Atlassian (in this case - rPath, Inc.).
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
...
Vendor: Atlassian Software Systems Pty Ltd
System Event Listeners - 1.0
Vendor: Atlassian Software Systems
System Notifications - 1.0
Vendor: Atlassian Software Systems Pty Ltd
System Repositories - 1.0
Vendor: Atlassian Software Systems Pty Ltd
System Web Panels and Renderers - 1.0
Vendor: Atlassian Software Systems Pty Ltd
System Web Resources - 1.0
Vendor: Atlassian Software Systems Pty Ltd
Trigger Reasons - 1.0
Vendor: Atlassian Software Systems Pty Ltd
VCS Version Collector - 1.0
Vendor: Atlassian Software Systems Pty Ltd
hg - 2.6.2-SNAPSHOT
Vendor: rPath, Inc.Resolution
Atlassian doesn't support third party plugins, and doesn't guarantee that it will work properly with Bamboo.
Disable third party plugins by deleting them from WEB-INF/lib directory or removing them from Bamboo's classpath and restart Bamboo.
If you really need/want to use any third party products with Bamboo, please contact the author of that product. In addition, feel free to use Atlassian Answers or contact our partners for help.
Was this helpful?