Use getWorkSpace instead of getModuleRoot to set the working directory #6

Merged
merged 1 commit into from Nov 5, 2012

Conversation

Projects
None yet
4 participants
Contributor

vsnijders commented Nov 2, 2012

Some SCMs (e.g. SVN) support checking out multiple modules into the same
workspace. In that case the getModuleRoot is not deterministic anymore.
Even if only one module is checked out, the Module Root is not
necessarily the same as the Work Space directory. So explicitly use
getWorkSpace to conform to the documented behavior: "the current working
directory of the command execution is always the job's workspace root."

@vsnijders vsnijders Use getWorkSpace instead of getModuleRoot to set the working directory
Some SCMs (e.g. SVN) support checking out multiple modules into the same
workspace. In that case the getModuleRoot is not deterministic anymore.
Even if only one module is checked out, the Module Root is not
necessarily the same as the Work Space directory. So explicitly use
getWorkSpace to conform to the documented behavior: "the current working
directory of the command execution is always the job's workspace root."
8d0afa9

Jenkins » xshell-plugin #8 SUCCESS
This pull request looks good
(what's this?)

mambu merged commit 3c8ade8 into jenkinsci:master Nov 5, 2012

Contributor

davehunt commented on 8d0afa9 Nov 6, 2013

I believe this has caused a regression where the repository is cloned to a subdirectory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment