![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
subversion |
|
Created:
|
02/May/13 2:21 AM
|
|
Description:
|
The help text associated with the "local module directory" field states:
Specify a local directory (relative to the workspace root) where this module is checked out. If left empty, the last path component of the URL is used as the default, just like the svn CLI. A single period (.) may be used to check out the project directly into the workspace rather than into a subdirectory.
I can't imaging a situation where one would ever want to check out a code module into a custom sub-folder that is found relative to the "workspace root" instead of the workspace folder being used for the current job.
Also, I would intuitively expect this relative path to respect any settings applied to the "custom workspace" field under the advanced project options area as well, so if specified the local module folder would be relative to whatever the custom workspace path resolves to (e.g.: whether it has an absolute or relative path).
|
|
Environment:
|
Windows 7 x64
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kevin Phillips
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
