[JIRA] [github-branch-source-plugin] (JENKINS-35657) Support Multibranch Workflow from 2 different github repos

1 view
Skip to first unread message

bryden.oliver@software.dell.com (JIRA)

unread,
Jun 12, 2016, 10:58:02 PM6/12/16
to jenkinsc...@googlegroups.com
Bryden Oliver created an issue
 
Jenkins / Improvement JENKINS-35657
Support Multibranch Workflow from 2 different github repos
Issue Type: Improvement Improvement
Assignee: Jesse Glick
Components: github-branch-source-plugin
Created: 2016/Jun/13 2:57 AM
Priority: Minor Minor
Reporter: Bryden Oliver

Currently you can specify multiple github sources in the configuration of a multibranch workflow project.
However when it comes to resolving the headcommit for the triggering source, it defaults to looking in the repository for the first source. This is the result of that:
hudson.plugins.git.GitException: Failed to fetch from https://github.com/**************************.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe -c core.askpass=true fetch --tags --progress https://github.com/*******************.git +refs/heads/:refs/remotes/origin/" returned status code -1:
stdout:
stderr:
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1463)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:808)
... 8 more

GitHub has been notified of this commit’s build result

ERROR: null
Finished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

bryden.oliver@software.dell.com (JIRA)

unread,
Jun 14, 2016, 10:36:01 PM6/14/16
to jenkinsc...@googlegroups.com
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

jglick@cloudbees.com (JIRA)

unread,
Jun 15, 2016, 6:35:01 PM6/15/16
to jenkinsc...@googlegroups.com

Not clear to me what the actual use case is here. Multiple forks of the same repository?

bryden.oliver@software.dell.com (JIRA)

unread,
Jun 15, 2016, 9:26:02 PM6/15/16
to jenkinsc...@googlegroups.com

My particular use case is having 2 repositories, one a server and one a client, so disjoint but related.
We want to have one build that grabs source from both and then builds them together particularly for testing purposes.

The changes I proposed means that for any change in repo A or repo B, it kicks off a build and manages all the branches that are open in either repo.
All for a little bit of safety in the code, that covers the case that the config UI allows you to do, but currently just fails if you do use it.

bryden.oliver@software.dell.com (JIRA)

unread,
Jun 23, 2016, 11:04:03 PM6/23/16
to jenkinsc...@googlegroups.com

The duplicate issue covers far more and seems to involve a far more complicated solution. Although the solution proposed here could probably cover the case mentioned in the other issue, or at least a significant subset of them.

jglick@cloudbees.com (JIRA)

unread,
Jul 5, 2016, 2:48:01 PM7/5/16
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Duplicate
 

Your use case definitely sounds like JENKINS-32018. The current plugin design is not intended to handle this.
Change By: Jesse Glick
Status: Open Resolved
Resolution: Duplicate
Reply all
Reply to author
Forward
0 new messages