|
||||||||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
AbstractProject.customWorkspace that is, which seems to be used in lieu of getWorkspaceFor. In fact freestyle projects do not acquire a lock when customWorkspace is used, meaning it is senseless to emulate that behavior.
It could make sense to offer an alternative workspace to the ws step, probably as a path relative to the slave root. You can already run whatever you like in any other location using the dir step, but there is no lock on the workspace in that case.