[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources [~rodrigc]: 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 "non production ready" 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources [~rodrigc]: 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 " non production ready 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources [~rodrigc]: For GitHub, this would require you have an internal Web Service Git Hook server, as GitHub internal 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. # 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources [~rodrigc]: For GitHub, this would require you have an internal Web Service Git Hook server, as GitHub internal nor enterprise has support for server side hooks. I use the Workflow plugin to wrap 3 jobs: Checkout 1, Checkout 2, BuildI 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. # 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin commented on JENKINS-7192 Re: Use multiple SCM sources Craig Rodrigues: For GitHub, this would require you have an internal Web Service Git Hook server, as GitHub internal nor enterprise has support for server side hooks. 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. 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin commented on JENKINS-7192 Re: Use multiple SCM sources 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources 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+PluginThis needs reopened as it should be a core part of Jenkins.The multi-scm plugin does NOT work well with CI / GitHub integration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin reopened an issue 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. Jenkins / JENKINS-7192 Use multiple SCM sources Change By: James Sandlin Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin edited a comment on JENKINS-7192 Re: Use multiple SCM sources 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Title: Message Title James Sandlin updated an issue Jenkins / JENKINS-7192 Use multiple SCM sources Change By: James Sandlin 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Craig Rodrigues commented on JENKINS-7192 Use multiple SCM sources I use Multiple SCMs plugin quite a bit. It has limitations as Oleg has pointed out, but for most simple cases it works well enough. A lot of the Jenkins developers are recommending using the new Workflow plugin to check out code from multiple repositories. I haven't tried Workflow yet, but that might be an option to consider. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Oleg Nenashev resolved JENKINS-7192 as Fixed Use multiple SCM sources Multiple SCMs Plugin resolves the case Change By: Oleg Nenashev (26/May/14 5:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Daniel Beck commented on JENKINS-7192 Use multiple SCM sources Oleg: Multiple SCM Plugin looks a bit like a hack. An overhaul of the core SCM api (including real support for multi-module checkouts in repo browsers) might be a good idea. That being said, I've not used it in production how well does it really work? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7192) Use multiple SCM sources
Oleg Nenashev commented on JENKINS-7192 Use multiple SCM sources It works... eventually Actually, the behavior depends on the plugin, because the current version does not support the "newInstance" method (see https://github.com/jenkinsci/multiple-scms-plugin/pull/4). Other basic checkout polling methods work well, but I'm almost sure that there're many bugs for more complex cases (like workspace cleanup hooks or various ItemListeners). In general, the plugin stills a hack. I confirm that the plugin works for Subversion, Perforce (fixed in the latest version), FileSCM and Git (for primitive configurations). BTW, the plugin requires the accurate configuration. Otherwise, there's a high risk of workspace collisions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
