Details
-
Type:
New Feature
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Component/s: mercurial-plugin
-
Labels:None
Description
I'd like to see an option, similar to that in the SVN plugin, that lets you add multiple Mercurial repositories to a Hudson job.
I realize this has been addressed in JENKINS-1143 and JENKINS-1344, but I think that this feature should be reconsidered. First of all, as stated in JENKINS-1344, not every collection of repositories will be organized in a forest. The forest extension itself is not bundled with Mercurial and, according to their wiki page, "does not appear to be actively maintained".
http://mercurial.selenic.com/wiki/ForestExtension
So I think that these days (the above issues are 2 years old), most projects will either use multiple but unrelated Mercurial repositories or they will use subrepos (which, I think, are still considered "experimental"), but not the forest extension.
Issue Links
- duplicates
-
JENKINS-4838
Subrepo support
-
- Open
-
- is related to
-
JENKINS-7192
Use multiple SCM sources
-
- Resolved
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Duplicate [ 3 ] |
| Link | This issue duplicates JENKINS-4838 [ JENKINS-4838 ] |
| Resolution | Duplicate [ 3 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
I don't think such a feature should be implemented in SCM plugins. If there is a need for this, Hudson core should support having multiple SCM configurations (possibly of different types!) active on different parts of the workspace.
| Link |
This issue is related to |
I joined specificially so that I could vote on this issue.
Do to the way our project was originally laid out, we have to use a custom workspace in order to build, and each project requires at least two clones from our centralized Mercurial repositories. This is, of course, something that I am actively working to fix, but the downside is that until I can completely refactor 89 separate Visual Studio projects, I'm stuck. I would prefer to get it working in its current state, and then slowly change things for the better.
Sure this is valuable, but I think it should be implemented in the core, not in the SCM plugin.
It looks like there may be a plugin that provides a proof-of-concept of this type of functionality (configuring multiple SCMs for a single workspace)
https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin
The Multiple SCMs Plugin seems to do a decent job. The only thing I see missing is a working MultiSCMRepositoryBrowser; no clue how that would be implemented, but seems to be nonessential.
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
Sorry, but this ticket was not asking for subrepo support, so it's not a duplicate.
The SVN plugin lets you check out from several unrelated repositories. I'd like to see this same feature in the Mercurial plugin, please.