-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.656
jobConfigHistory plugin 2.14
I see exceptions similar to the following in our Jenkins system log. We are running Jenkins 1.656. I asked for help first on the mailing list but got no reply. I am not sure which component is at fault - perhaps the jobConfigHistory plugin?
java.lang.RuntimeException: Could not create rootDir /var/lib/jenkins/config-history/jobs/Zodiac_gcc_all_branches_and_trunk/branches/trunk/2016-06-06_14-37-52 at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryDir(FileHistoryDao.java:241) at hudson.plugins.jobConfigHistory.FileHistoryDao.getRootDir(FileHistoryDao.java:129) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntry(FileHistoryDao.java:409) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:259) at hudson.plugins.jobConfigHistory.FileHistoryDao.saveItem(FileHistoryDao.java:270) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:54) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:513) at hudson.model.Job.save(Job.java:180) at hudson.model.AbstractProject.save(AbstractProject.java:305) at hudson.model.AbstractProject.setScm(AbstractProject.java:1563) at com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject._syncBranches(AbstractMultiBranchProject.java:1038) at com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject.syncBranches(AbstractMultiBranchProject.java:948) at com.github.mjdetullio.jenkins.plugins.multibranch.SyncBranchesTrigger.run(SyncBranchesTrigger.java:102) at com.github.mjdetullio.jenkins.plugins.multibranch.SyncBranchesTrigger.checkTriggers(SyncBranchesTrigger.java:255) at com.github.mjdetullio.jenkins.plugins.multibranch.SyncBranchesTrigger$Cron.doRun(SyncBranchesTrigger.java:230) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
- is related to
-
-
- Open
-
[JENKINS-35421] Exception: "Could not create rootDir"
David Aldrich
created issue -
David Aldrich
added a comment - Thanks for your reply.
That directory does not exist. The directory specified by the exceptions has many different values but they are all for June:
/var/lib/jenkins/config-history/jobs/Zodiac_gcc_all_branches_and_trunk/branches/trunk/2016-06*
and none of them exist.
David Aldrich
added a comment - Thanks for your reply.
That directory does not exist. The directory specified by the exceptions has many different values but they are all for June:
/ var /lib/jenkins/config-history/jobs/Zodiac_gcc_all_branches_and_trunk/branches/trunk/2016-06*
and none of them exist. David Aldrich
added a comment - Can you help me further with this please? The multi branch plugin has a very own kind to use job configurations and this isn't compatible with the kind how the config history plugin normally handle it.
At them moment we have no solutions for different problems with this plugin but we work on this.
Please be patient.
David Aldrich
added a comment - No problem, thank you for your answer. Perhaps I should disable the job config history plugin for now.
David Aldrich
added a comment - No problem, thank you for your answer. Perhaps I should disable the job config history plugin for now. I tried to reproduce this issue. JobConfigHistory stores config changes on the main project as well as on all branches and I don't see any exception like that one above. All directories exist.
You mentioned, that the problematic jobs are all from June. Did you use JobConfigHistory before June without problems?
Does this exception only occur on multi branch jobs or on all jobs?
David Aldrich
added a comment - Thanks for investigating this issue. I have disabled the JobConfigHistory plugin and restarted the system, so I no longer have the system log.
Yes, I used JobConfigHistory before June without problems.
I think the exception only occurred on multi-branch jobs but I can't be sure.
David Aldrich
added a comment - Thanks for investigating this issue. I have disabled the JobConfigHistory plugin and restarted the system, so I no longer have the system log.
Yes, I used JobConfigHistory before June without problems.
I think the exception only occurred on multi-branch jobs but I can't be sure. If someone can explain or reproduce this scenario, then feel free to reopen this ticket.
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Yes, this is a exception of JobConfigHistory. Can you check, if the directory
/var/lib/jenkins/config-history/jobs/Zodiac_gcc_all_branches_and_trunk/branches/trunk/2016-06-06_14-37-52exists?
Does this exception occur more ofter?