Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7155

Support multiple Mercurial repositories per job

    XMLWordPrintable

    Details

    • Similar Issues:

      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.

        Attachments

          Issue Links

            Activity

            Hide
            dhaun Dirk Haun added a comment -

            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.

            Show
            dhaun Dirk Haun added a comment - 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.
            Hide
            jglick Jesse Glick added a comment -

            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.

            Show
            jglick Jesse Glick added a comment - 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.
            Hide
            moswald Matt Oswald added a comment -

            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.

            Show
            moswald Matt Oswald added a comment - 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.
            Hide
            jglick Jesse Glick added a comment -

            Sure this is valuable, but I think it should be implemented in the core, not in the SCM plugin.

            Show
            jglick Jesse Glick added a comment - Sure this is valuable, but I think it should be implemented in the core, not in the SCM plugin.
            Hide
            davidmc24 davidmc24 added a comment -

            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

            Show
            davidmc24 davidmc24 added a comment - 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
            Hide
            jglick Jesse Glick added a comment -

            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.

            Show
            jglick Jesse Glick added a comment - 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.
            Hide
            greenscar James Sandlin added a comment - - edited

            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."? - https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin

            This needs reopened as it should be a core part of Jenkins.

            The multi-scm plugin does NOT work well with CI / GitHub integration.

            Show
            greenscar James Sandlin added a comment - - edited 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."? - https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin This needs reopened as it should be a core part of Jenkins. The multi-scm plugin does NOT work well with CI / GitHub integration.
            Hide
            greenscar James Sandlin added a comment - - edited

            The multi-scm plugin (which was never intended more than a POC) works fine until you attempt to do CI. At this point, the lack of real integration and capabilities breaks.

            1. Jenkins has job / env vars for only 1 GIT repo.
            2. The HTML display just says "Git Build Data" and "No Tags" for each repo. I must iterate through each of these links to find the repo I'm interested in.
            3. The order of the repos in the list is critical to which env var Jenkins picks up.
            Show
            greenscar James Sandlin added a comment - - edited The multi-scm plugin (which was never intended more than a POC) works fine until you attempt to do CI. At this point, the lack of real integration and capabilities breaks. Jenkins has job / env vars for only 1 GIT repo. The HTML display just says "Git Build Data" and "No Tags" for each repo. I must iterate through each of these links to find the repo I'm interested in. The order of the repos in the list is critical to which env var Jenkins picks up.

              People

              Assignee:
              kohsuke Kohsuke Kawaguchi
              Reporter:
              dhaun Dirk Haun
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: