-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
Not applicable
We have certain projects that pull modules from both CVS and SVN. The way we do it right now it to pull from SVN using the plugin, and then use the "Execute Shell" to pull from CVS using the command line. It would be awesome if we could use both (may be change the radio buttons to a check boxes?) for the same project.
- is duplicated by
-
JENKINS-9720 Support multiple SCM types within the one job
-
- Resolved
-
-
JENKINS-5158 Add support for multiple Source Code Management types in single job
-
- Resolved
-
- is related to
-
JENKINS-7155 Support multiple Mercurial repositories per job
-
- Reopened
-
[JENKINS-7192] Use multiple SCM sources
Description | Original: We have certain projects that pull modules from both CVS and SVN. The way we do it right now it to pull from SVN using the plugin, and then use the "Execute Shell" to pull from CVS. It would be awesome if we could use both (may be change the radio buttons to a check boxes?) for the same project. | New: We have certain projects that pull modules from both CVS and SVN. The way we do it right now it to pull from SVN using the plugin, and then use the "Execute Shell" to pull from CVS using the command line. It would be awesome if we could use both (may be change the radio buttons to a check boxes?) for the same project. |
Link | New: This issue is related to JENKINS-2947 [ JENKINS-2947 ] |
Link | Original: This issue is related to JENKINS-2947 [ JENKINS-2947 ] |
Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Link | New: This issue is related to JENKINS-7155 [ JENKINS-7155 ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Comment |
[ How can you close this ticket when the multi-scm plugin clearly states: "This plugin is more of a proof-of-concept than a robust and fully functional component. It does work in my particular build environment, and is meant to serve as a demonstration of what might be possible with more work. It was inspired by JENKINS-7155 requesting multiple repository checkouts for Mercurial similar to what is possible with the Subversion plugin. It's currently implemented as a plugin, but if enough people find it useful, I think the idea would work better in the Jenkins core."? This needs reopened as it should be a core part of Jenkins. The multi-scm plugin does NOT work well with CI / GitHub integration. ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |