|
||||||||
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.
The section in a freestyle job's configuration where you can set a custom workspace is called 'Advanced Project Options' and hidden by default. Just meant that while it's included in Jenkins core, it's usually not something you should need to use (and brings you slightly nearer to unknown "here be dragons" territory).
You could use Jenkins just for triggering your batch script at the cost of an additional copy of the source code (unless you can configure it to do a sparse/non-recursive/... checkout, in which case it's cheaper). Do everything else as you would from a standalone script.
Yeah, we've also gone into use-Jenkins-for-everything-happening-on-a-server mode. But the limitations (e.g. limited interactivity) clearly show.
You can find the mailing lists here: http://jenkins-ci.org/content/mailing-lists (via the 'Connect' menu item).
If you use the "workspace" mostly to provide a remote read-only file browser, there might be an easy solution to provide that for arbitrary directories. Let me know.