[JIRA] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title James Nord commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories Why would you need to refer anything of the CI environment? URLs? I don't follow. Tools (you need a specific one to build!) : (maven / JDK etc) may have different names Credentials (maybe for deploying you deploy as you - I deploy as me): IDs may not match Labels (where to build it): you may say linux - I may say RedHat 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] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Flávio Augusto Valones commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories +1 for the SCMSource approach! 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] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Antonio Muñiz commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories because it has to refer to a particular CI environment Why would you need to refer anything of the CI environment? URLs? I don't follow. 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] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Andrew Bayer commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories Yeah, I'm used to living in a world of meta-repos that have scripts, repo and branch information, etc for pulling other repositories into the build process along the way, which right now doesn't quite organically fit into Multibranch. Mind you, it's a bit of a challenge to rationalize the meta-repo with the child repos in re: versioning without something like you said, submodules, Repo, etc. I'd be a strong +1 for such an SCMSource - coupling would be handy. 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] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-32018 Multibranch workflow project tracking multiple repositories Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 10/Dec/15 8:10 PM Labels: multibranch Priority: Major Reporter: Jesse Glick In some cases it is inappropriate to keep Jenkinsfile in the same repository as project sources, because it has to refer to a particular CI environment that not all users care about. There are other cases where multiple repositories must be consulted during the course of the build. In all these cases currently you can use a standalone Workflow project to run builds, but you lose the advantages of multibranch: ability to see the effect of changes made in unmerged branches ability to customize Jenkinsfile atomically to match other changes, where relevant One possibility is another mode for workflow-multibranch, where the script comes not from a coversioned
