[JIRA] (JENKINS-8082) git plugin multi-repo can't work

2013-03-20 Thread da...@walend.net (JIRA)














































David Walend
 commented on  JENKINS-8082


git plugin multi-repo cant work















git subtrees  http://git-scm.com/book/en/Git-Tools-Subtree-Merging  did a fine job delivering the multiple repository feature for me. (Submodules are much less ergonomic.)



























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/groups/opt_out.




[JIRA] (JENKINS-8082) git plugin multi-repo can't work

2013-03-19 Thread da...@walend.net (JIRA)














































David Walend
 commented on  JENKINS-8082


git plugin multi-repo cant work















I suggest reopening this and "fix" it by changing the UI to expressly state that any extra repositories are just backup locations and not really multiple, different repositories for separate software. It seduced me into believing it was what I needed, and turned out to be not useful. (It seems a little dangerous to rely on a backup repository. How do you know what you're building?)

Also, not handling multiple git repositories is a huge missing feature. Any update on when we'll get it?



























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/groups/opt_out.




[JIRA] (JENKINS-8082) git plugin multi-repo can't work

2012-08-07 Thread lk.prasa...@gmail.com (JIRA)














































Prasanna L
 commented on  JENKINS-8082


git plugin multi-repo cant work















abayer,
The documentation on multiple scm plugins notes that it is tested only with Mercurial and Subversion plugins. Have you used it successfully with git repositories? 



























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






[JIRA] (JENKINS-8082) git plugin multi-repo can't work

2012-03-01 Thread crw...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159724#comment-159724
 ] 

crwong commented on JENKINS-8082:
-

I am not sure I understand why this is marked as Won't Fix.  The Hudson 
version of the git plugin is marked as Fixed.  

I have one project that has its source in one repo and the framework that it 
uses in another repo, and I would like to be able to use the plugin to pull 
both the source for the project and the source for the framework.

 git plugin multi-repo can't work
 

 Key: JENKINS-8082
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8082
 Project: Jenkins
  Issue Type: Bug
  Components: git
Affects Versions: current
 Environment: git plugin 1.1
Reporter: bwilliams
Assignee: abayer

 In the git plugin, you have the ability to watch multiple repos, but then you 
 clone them into the same dir, so the git checkouts show you all of one repo, 
 but not the others.
 The local subdirectory for repo and probably branches to build need to be 
 per repository, not for all.

--
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