Moved Workspace Root Directory; Jenkins Ignores It

[Trinition]

I have a simple master-only set up (Jenkins 1.596), but I was low on disk
space, so I moved my workspaces to a second disk:

1. Set up the new location (e.g. E:\Workspace)
2. Changed Jenkins "Workspace Root Directory" to "
E:/Workspace/${ITEM_FULLNAME}"
3. Shut down Jenkins
4. Move old Workspace contents to new one
5. Started Jenkins

When wen to one of my jobs, and clicked on its Workspace, Jenkins
complained that there was no workspace. The error message even included a
path -- but it was the *wrong path*!


*There's no workspace for this project. Possible reasons are:*


1. *The project was renamed recently and no build was done under the new
name.*
2. *The slave this project has run on for the last time was removed.*
3. *The workspace directory (C:\Program Files
(x86)\Jenkins\workspace\CIN.Code Trunk) is removed outside Jenkins.*
4. *The workspace was wiped out and no build has been done since
then.*

*Run a build to have Jenkins create a workspace.*

I went back into my Jenkins configuration and verified that the Workspace
Root Directory is still set to my new path.

Is there another step?

[Trinition]

I don't understand it, but here's my resolution:

While clicking on the workspace of any job would produce that error, if I
kicked off a build, the build worked... from the *new* workspace folder.
And then the workspace worked fine for that job from then on.

So I'm guessing the Workspace link in the page for a Jenkins job looks at
what workspace was last used, not what the workspace should be from now on?

Post by Trinition
I have a simple master-only set up (Jenkins 1.596), but I was low on disk
1. Set up the new location (e.g. E:\Workspace)
2. Changed Jenkins "Workspace Root Directory" to "
E:/Workspace/${ITEM_FULLNAME}"
3. Shut down Jenkins
4. Move old Workspace contents to new one
5. Started Jenkins
When wen to one of my jobs, and clicked on its Workspace, Jenkins
complained that there was no workspace. The error message even included a
path -- but it was the *wrong path*!
*There's no workspace for this project. Possible reasons are:*
1. *The project was renamed recently and no build was done under the
new name.*
2. *The slave this project has run on for the last time was removed.*
3. *The workspace directory (C:\Program Files
(x86)\Jenkins\workspace\CIN.Code Trunk) is removed outside Jenkins.*
4. *The workspace was wiped out and no build has been done since
then.*
*Run a build to have Jenkins create a workspace.*
I went back into my Jenkins configuration and verified that the Workspace
Root Directory is still set to my new path.
Is there another step?