-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execution of git-commit-id-plugin in Docker build fails #518
Comments
https://community.sonarsource.com/t/error-locking-filebasedconfig-root-config-jgit-config-failed-after-5-retries/21899 apparently also describes a workaround that could be used, if a newer JGit version doesn't fix the problem. |
Hello, Some questions:
Since this seems to be a JGit issue you should also be able to bypass the problem by setting Besides that I don't think i can do much from the plugin perspective (just waiting until JGit fixed the issue or using the native git binary as suggested) |
I am using
Unfortunately if I execute that on my (Windows) machine I cannot reproduce the problem, while the Bamboo build fails every time (Linux). However, thanks a lot for your suggestions! I tried them both:
|
Describe the bug
Building with standard configuration from Bamboo in Docker image (mounting project directory with git repository) fails with
Steps to Reproduce
Execute
mvn clean package
in docker container from Bamboo build, project directory mounted as/data
.Expected behavior
Error should not occur.
Additional context
I don't know if the git-commit-id-plugin uses JGit behind the scenes, but this seems to be the same problem as described here: https://community.sonarsource.com/t/error-locking-filebasedconfig-root-config-jgit-config-failed-after-5-retries/21899.
I suspect that this is happening, because the JGit config is created inside the
/root
directory of the docker container, which is a different drive than/data
drive where the git repo is mounted.I did open an eclipse bug for JGit: https://bugs.eclipse.org/bugs/show_bug.cgi?id=566170
The text was updated successfully, but these errors were encountered: