-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
I was using Jenkins with a single project/job with no issues.
Recently added a new project/job and strange things started to happen.
In the beginning builds were shared among both projects and showing as if they were part of both. I cloned the jobs to try to fix the issues but didn't helped.
After some copies, restarts and re-reads of config from disk I got it to a state where at least builds show separately for each project but project status is shared between the two I have now.
You can see this in the screenshot attached.
I'm using version: 1.568
[JENKINS-23508] Duplicated status info for many projects on dashboard
Lluís M. García
added a comment - Ok, done that and now the build process is showing this:
Building in workspace /var/lib/jenkins/jobs/feed-engine/workspace
java.io.IOException: Failed to mkdirs: /var/lib/jenkins/jobs/feed-engine/workspace
at hudson.FilePath.mkdirs(FilePath.java:1075)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1245)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530)
at hudson.model.Run.execute(Run.java:1732)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)
even when the folder exists:
ls -lah /var/lib/jenkins/jobs/feed-engine/workspace
total 8.0K
drwxr-xr-x 2 jenkins jenkins 4.0K Jun 24 11:39 .
drwxr-xr-x 7 jenkins jenkins 4.0K Jun 24 11:39 ..
Lluís M. García
added a comment - Ok, done that and now the build process is showing this:
Building in workspace /var/lib/jenkins/jobs/feed-engine/workspace
java.io.IOException: Failed to mkdirs: /var/lib/jenkins/jobs/feed-engine/workspace
at hudson.FilePath.mkdirs(FilePath.java:1075)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1245)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530)
at hudson.model.Run.execute(Run.java:1732)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)
even when the folder exists:
ls -lah /var/lib/jenkins/jobs/feed-engine/workspace
total 8.0K
drwxr-xr-x 2 jenkins jenkins 4.0K Jun 24 11:39 .
drwxr-xr-x 7 jenkins jenkins 4.0K Jun 24 11:39 .. Lluís M. García
added a comment - Apparently there were two issues here:
- Wrong configured builds directories: this was changed but our sysadmin and he did it the wrong way. There should be a mechanism to check that at least one of the variables is there.
- Wrong partition permissions. Apparently the user had no rights to write at that partition even if I chmo'd for it.
The first one should be considered to avoid unnecessary headaches.
Lluís M. García
added a comment - Apparently there were two issues here:
Wrong configured builds directories: this was changed but our sysadmin and he did it the wrong way. There should be a mechanism to check that at least one of the variables is there.
Wrong partition permissions. Apparently the user had no rights to write at that partition even if I chmo'd for it.
The first one should be considered to avoid unnecessary headaches. 
In the global configuration, click the 'Advanced' button near the top right and check the configured builds directory. It absolutely must refer to 'ITEM_FULL_NAME', 'ITEM_FULLNAME' or 'ITEM_ROOTDIR'.