Mark Waite edited a comment on New Feature JENKINS-27668

I also think that identifying the repo name on local workspace is needed for every SCM plugin. For example, if we take Multi-SCM plugin which configures a TFS project ($/Project1/Source) and a Git repo http://gitstore-host/project2.git (sub directory starts with Source directory) - then the directories from both SCM tool will be merged and create junk workspace useful for nothing.

I don't know if the TFS plugin works with the multi-SCM plugin, but the git plugin does work with it, and allows the user to specify a subdirectory of the workspace for each of the repositories used in that job. With the git plugin, after I've added the git repository to the Multi-SCM configuration of the job, then I need to add an "Additional behaviour" to that git configuration to checkout to a specific subdirectory.

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.

Reply via email to