-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: git-client-plugin, remoting
-
Labels:None
-
Environment:ubuntu 18.04
Jenkins ver. 2.164.3
-
Similar Issues:
Building remotely on jenkins-worker-ub-1 (h5sync worker-production) in workspace /var/lib/jenkins/submodule_only/mytaskBuilding remotely on jenkins-worker-ub-1 (h5sync worker-production) in workspace /var/lib/jenkins/submodule_only/mytaskAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to jenkins-worker-ub-1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.mkdirs(FilePath.java:1243) at hudson.model.AbstractProject.checkout(AbstractProject.java:1202) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.nio.file.AccessDeniedException: /var/lib/jenkins at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3229) at hudson.FilePath.access$1300(FilePath.java:210) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1251) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1247) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3042) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
If the folder only exists on the server and not on the worker, but the worker is attempting to create something at that location, then it likely means there is a configuration error in your job definition or your server definition. You'll need to find that configuration error and correct it. That is not something the git plugin can correct for you.
There is a permission problem on the agent where the git command is being attempted. The stack trace reports:
That may mean that the directory does not exist and the process does not have permission to create it, or that the permissions are incorrect on the directory.
It could be that the job is mistakenly configured to use a specific directory path instead of allowing Jenkins to manage the directory path. It could be that the agent process is running as the wrong user. It could be a misconfigured agent working directory value.