|
||||||||
|
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/groups/opt_out.
Yup. I've tried "Use custom workspace" but it doesn't do what I want. Regardless of what $WORKSPACE is set to, everything is checked out in $WORKSPACE... I want to be able to specify an alternative directory to checkout in, relative to $WORKSPACE.
Specifically I have several cases:
1) If the Component is well formed (e.g. the component name is FuBar and it contains only one top-level directory FuBar) then I'd like to check the contents of FuBar out to the root of $WORKSPACE
2) For components that aren't well formed (e.g. the component name is FuBar and it contains multiple top-level files and directories) then I want to check the contents out at $WORKSPACE/rtc-ws/ (for example).
In addition, I need case 2 for when doing Maven releases, because the Maven Release Plugin cannot checkout a second copy of the repository (needed for some odd reason) within the target directory. This is a known limitation with Jazz SCM. To work around it I need to create a second directory (e.g. $WORKSPACE/release-copy) and tell Maven to use that for the release. There must not be a $WORKSPACE/.jazz directory in this case.
Obviously I can remove the .jazz directory in a pre-build step, but that seems rather disgusting to me and I'm unclear if it would effect the TeamCenter plugin.
Hopefully I was clear in my description.