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

Use multiple SCM sources

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Not applicable
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            greenscar James Sandlin added a comment - - edited

            Craig Rodrigues: For GitHub, this would require you have an internal Web Service Git Hook server, as neither github.com nor self hosted enterprise has support for server side hooks.

            An example:

            1. I use the Workflow plugin to wrap 3 jobs: Checkout 1, Checkout 2, Build
            2. I have a GitHook server which is called by a GitHub Hook on push or merge request.
            3. This web service then calls the Jenkins job mentioned above.

            Small companies cannot afford to maintain a GitHub Hook webserver and depend upon Jenkins capabilities.

            Specific limitations of Jenkins even when using this "proof-of-concept" multi-scm plugin:

            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.

            If the Jenkins team is proposing their team does not work with GitHub / CI, this solution is good to go. Otherwise, the team needs to rethink the solution.

            Show
            greenscar James Sandlin added a comment - - edited Craig Rodrigues : For GitHub, this would require you have an internal Web Service Git Hook server, as neither github.com nor self hosted enterprise has support for server side hooks. An example: I use the Workflow plugin to wrap 3 jobs: Checkout 1, Checkout 2, Build I have a GitHook server which is called by a GitHub Hook on push or merge request. This web service then calls the Jenkins job mentioned above. Small companies cannot afford to maintain a GitHub Hook webserver and depend upon Jenkins capabilities. Specific limitations of Jenkins even when using this "proof-of-concept" multi-scm plugin: 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. If the Jenkins team is proposing their team does not work with GitHub / CI, this solution is good to go. Otherwise, the team needs to rethink the solution.
            Hide
            jglick Jesse Glick added a comment -

            Jenkins Pipeline addresses this as a core feature, so I think this can be closed—we do not plan to implement it in freestyle projects.

            Show
            jglick Jesse Glick added a comment - Jenkins Pipeline addresses this as a core feature, so I think this can be closed—we do not plan to implement it in freestyle projects.
            Hide
            wilson_ds_net Brian Wilson added a comment -

            The Jenkins Pipeline is way over complicated for this simple need. I'm really surprised this hasn't come up before. If you aren't going to provide this feature, you could at lease direct users to an example of how to set up the complicated pipeline process so they have a clue as to what to do. Please re-evaluate your priorities and look at implementing a check box, rather than radio button idea for setting up access to multiple SCM repositories.

            Show
            wilson_ds_net Brian Wilson added a comment - The Jenkins Pipeline is way over complicated for this simple need. I'm really surprised this hasn't come up before. If you aren't going to provide this feature, you could at lease direct users to an example of how to set up the complicated pipeline process so they have a clue as to what to do. Please re-evaluate your priorities and look at implementing a check box, rather than radio button idea for setting up access to multiple SCM repositories.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            "We" in the message below meant "jglick", no more. We have no such roadmap decisions.

            If somebody wants to implement the feature, such contribution will be really appreciated. It could be done via SCM API extension and integration, but it's definitely not a trivial task

            Show
            oleg_nenashev Oleg Nenashev added a comment - "We" in the message below meant "jglick", no more. We have no such roadmap decisions. If somebody wants to implement the feature, such contribution will be really appreciated. It could be done via SCM API extension and integration, but it's definitely not a trivial task
            Hide
            greenscar James Sandlin added a comment -

            We actually migrated our primary product to Jenkins Pipeline (for a Fortune 500 company) and this has resolved our issue. Pipeline still has its limitations but is worth the migration.

            Show
            greenscar James Sandlin added a comment - We actually migrated our primary product to Jenkins Pipeline (for a Fortune 500 company) and this has resolved our issue. Pipeline still has its limitations but is worth the migration.

              People

              • Assignee:
                Unassigned
                Reporter:
                khushsk Sagar Khushalani
              • Votes:
                7 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated: