[ 
https://issues.jenkins-ci.org/browse/JENKINS-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163672#comment-163672
 ] 

Doug Borg commented on JENKINS-13086:
-------------------------------------

[~rmorgenstein], that is not exactly ideal as the multiple SCMs plugin does not 
support post-commit / post-update triggers. 

Furthermore, it just makes sense that the "Local subdirectory for repo" should 
be a per-repo option, not part of the global git configuration. Even the name 
of the option is confusing the way it is now and other SCM plugins have the 
ability to do this without having to resort to the Multiple-SCMs Plugin.
                
> Clone to directory named for repository
> ---------------------------------------
>
>                 Key: JENKINS-13086
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13086
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: git
>    Affects Versions: current
>            Reporter: Tom Haggie
>            Assignee: Nicolas De Loof
>            Priority: Minor
>              Labels: git, jenkins
>
> In a Jenkins Job you can select to use git to clone / pull from multiple 
> repositories but it always pulls straight to the working directory so if you 
> have multiple they end up overwriting each other.
> What I'd like is a checkbox to say clone to a directory (under the workspace) 
> named for the git repository.
> So (when checked) if I had the command as: 
> https://github.com/jenkinsci/jenkins.git
> it would checkout to .../workspace/job_name/jenkins

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to