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

jglick commented on JENKINS-4838:
---------------------------------

I do not know of anyone actively working on this. Since my organization does 
not use subrepos I am not inclined to work on it myself.

I would expect it to be a relatively difficult change, i.e. you would need to 
understand all aspects of the current plugin; handle (or explicitly forbid) 
interaction with various existing features such as caching & sharing, polling 
exclusions, and browsers, which are all written to assume that the portion of 
the workspace under consideration is the checkout of one node of one 
repository; and write a full JUnit suite detailing the expected behavior, 
ideally before starting to make changes to main sources.

Note that for jobs formerly using the Forest extension the recommendation is to 
use the Multi-SCM plugin instead - basically configuring a separate instance of 
the Mercurial plugin for each repo in the "forest". This seems to work fine, if 
perhaps a little more verbose to configure. But subrepos work differently due 
to `.hgsubstate`, so I doubt you could use the Multi-SCM plugin for this 
purpose.

Also beware of subrepos using foreign SCMs like Subversion; it is not clear 
whether or how the Mercurial plugin (in cooperation with other SCM plugins) 
could behave correctly with such a setup.
                
> Subrepo support
> ---------------
>
>                 Key: JENKINS-4838
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-4838
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: mercurial
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: jglick
>            Assignee: jglick
>
> In addition to supporting the Forest extension, it would be good to support 
> the
> new subrepo system in Hg 1.3+.

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