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

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

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.

great, thanks!

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

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

Seeing this issue with SCM Sync Configuration Plugin when the workspace is not in Jenkins home. It freezes the build flow with this error in the log.

Is the best workaround to not use a custom workspace so the workspace is in Jenkins home?

Any chance of getting this fixed?

Yup I don't see any other workaround ATM

This issue is not on my top level priority list, so PR are welcome

I am seeing the same issue in combination with other plugins such as the claim and disk usage plugins. We are using a separate workspace, build and JENKINS_HOME directory.

This also affects Jenkins 1.520 with SCM Sync Config 0.0.7.3.

I got the same issue, but using Jenkins 1.568 with Windows (SCM Sync Config 0.0.7.4). I cannot use the default install workspace path (C:\Program Files\Jenkins\..) as my git repo has many, many, many long nested folders and I hit the 260 characters windows file path limitation...

Fixed in 0.0.9