|
||||||||
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/d/optout.
It is enabled for a job when any folder in it's hierarchy has this enabled. So if FoldA/FoldB has the property set, it will be effective for FoldA/FoldB/job1 and FoldA/FoldB/FoldC/job2, but not for FoldA/job3 or job4. For the 'advanced' option to place the workspace inside the folder's workspace, it uses the configuration of the innermost/most deeply nested folder that has 'Use short workspace enabled'.
Example:
Then the following behavior will occur:
I'm not sure what you want to see. Windows Explorer? The build log mentions where the workspace is (for freestyle jobs at least, didn't try for Build Flow, and it looks like
(enabled) or (enabled and configured to place the short workspace inside the folder's workspace); rather than the default of:Results are similar on Windows, just e.g. C:\Jenkins rather than /var/lib/jenkins.