-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Ubuntu 11.10
Jenkins 1.461
SCM Sync Configuration Plugin 0.0.5
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
java.lang.IllegalArgumentException: Err ! File [/mnt/store/jenkins/CodeGenerationMaven/builds/2012-04-25_15-39-35/build.xml] seems not to reside in [/var/lib/jenkins] !
at hudson.plugins.scm_sync_configuration.JenkinsFilesHelper.buildPathRelativeToHudsonRoot(JenkinsFilesHelper.java:12)
at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:21)
at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:22)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:172)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:19)
at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78)
at hudson.model.Run.save(Run.java:1571)
at hudson.maven.MavenModuleSetBuild.setMavenVersionUsed(MavenModuleSetBuild.java:388)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
at hudson.model.Run.run(Run.java:1434)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-13593] Seems to not handle having builds in seperate folder
Christian Lövsund
created issue -
Christian Lövsund
added a comment - HOME /var/lib/jenkins
JENKINS_HOME /var/lib/jenkins
LANG en_US.UTF-8
LANGUAGE en_US:en
LD_LIBRARY_PATH /usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_31/jre/../lib/amd64
LOGNAME jenkins
MAIL /var/mail/jenkins
NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat
PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PWD /var/lib/jenkins
SHELL /bin/bash
SHLVL 1
TERM screen
USER jenkins
XDG_SESSION_COOKIE 2a2862c8d59aff8cfea5a5f000000010-1335363605.122239-652733116
XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt
Christian Lövsund
added a comment - HOME /var/lib/jenkins
JENKINS_HOME /var/lib/jenkins
LANG en_US.UTF-8
LANGUAGE en_US:en
LD_LIBRARY_PATH /usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_31/jre/../lib/amd64
LOGNAME jenkins
MAIL /var/mail/jenkins
NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat
PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PWD /var/lib/jenkins
SHELL /bin/bash
SHLVL 1
TERM screen
USER jenkins
XDG_SESSION_COOKIE 2a2862c8d59aff8cfea5a5f000000010-1335363605.122239-652733116
XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Christian Lövsund
added a comment - I got this Exception when trying to build any job in jenkins.
So I needed to uninstall/disable plugin in order to make Jenkins build any job.
It worked before I updated from version 0.0.4
I have a setup where all the build data (artifacts and all) is put on a big slower disk, while jenkins itself and all build occur on a SSD.
See picture for more info.
Christian Lövsund
added a comment - I got this Exception when trying to build any job in jenkins.
So I needed to uninstall/disable plugin in order to make Jenkins build any job.
It worked before I updated from version 0.0.4
I have a setup where all the build data (artifacts and all) is put on a big slower disk, while jenkins itself and all build occur on a SSD.
See picture for more info. Christian Lövsund
made changes -
| Attachment | New: jenkins.png [ 21770 ] |
Frédéric Camblor
added a comment - Wow ok this is related to this workspace root directory / build record root directory configuration stuff !
I think you're the first person I encounter using these fields 
I'll try to see if I can find a workaround about this special case..
Frédéric Camblor
added a comment - Wow ok this is related to this workspace root directory / build record root directory configuration stuff !
I think you're the first person I encounter using these fields
I'll try to see if I can find a workaround about this special case.. Christian Lövsund
added a comment - great, thanks! 
Alexander Alexeev
added a comment - Hi! I've same issue with SCM Sync Configuration Plugin.
I use Windows 2008 R2.
Jenkins home and build data is placed on different drives.
This issue has appeared when I upgrade Jenkins from 1.459 to 1.461
Alexander Alexeev
added a comment - Hi! I've same issue with SCM Sync Configuration Plugin.
I use Windows 2008 R2.
Jenkins home and build data is placed on different drives.
This issue has appeared when I upgrade Jenkins from 1.459 to 1.461 
Joe Mihalich
added a comment - At minimum the builds directory field is completely non functional. It updates the build-directory in the master config.xml but it does not even attempt to create the jobs in that directory. The jobs are always created in the jenkins home dir/jobs. It doesn't seem like this variable is meant to specify a jobs directory. The field description in the help doesn't match the field title. This field does not work for me in builds 459-461 (minimum). I don't know if they worked before those builds.
Anyway, as a work around till you figure this out, I just left the defaults alone, and deleted the jobs & workspace directory, and created them again as symlinks to the drive i wanted them created on. This seems to work fine.
The functionality we need for my purposes is a way to specify the directory where the workspaces go, and where the jobs go.
Thanks,
Joe
Joe Mihalich
added a comment - At minimum the builds directory field is completely non functional. It updates the build-directory in the master config.xml but it does not even attempt to create the jobs in that directory. The jobs are always created in the jenkins home dir/jobs. It doesn't seem like this variable is meant to specify a jobs directory. The field description in the help doesn't match the field title. This field does not work for me in builds 459-461 (minimum). I don't know if they worked before those builds.
Anyway, as a work around till you figure this out, I just left the defaults alone, and deleted the jobs & workspace directory, and created them again as symlinks to the drive i wanted them created on. This seems to work fine.
The functionality we need for my purposes is a way to specify the directory where the workspaces go, and where the jobs go.
Thanks,
Joe Frédéric Camblor
made changes -
| Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Hi Christian,
Can you confirm your JENKINS_HOME is /var/lib/jenkins (it should since this is what I get when I use Hudson.getInstance().getRootDir())
Do you know which plugin (or script) is generating this file ?
I need more context for your specific use, I could remove this exception check, but I could avoid it, I'd prefer