New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for multiple SCM plugin #171
Comments
I would suspect that it would be because we are explicitly setting the Git revision to build via RevisionParameterAction. I'm not sure how the multiple SCM plugin works. Perhaps there's a way to set the RevisionParameterAction to only be for a particular repo? Maybe the multiple SCM plugin folks know of a way. |
Thanks @valdisrigdon for your reply. I don't have much knowledge about jenkins plugin architecture but I found that multiple scm plugin call each scm's |
I'm seeing exactly the same: using the MultipleSCMs plugin, and despite having set the branch to
|
Searching online, it seems that other people are seeing the same behaviour, and that it was introduced some time after 1.9. I have zero knowledge of the internals but looking at the diffs after 1.9 I've found a couple suspicious commits, that have to do with the rev-parse command with Can you please have a look and see if some change could have introduced this? |
I just verified that this works properly in version 1.9. Which means that when using the MultipleSCMs plugin, the proper branch is checked out for each repository, and the |
Any workaround available for this? |
I'm also interested on a fix/workaround for this. |
+1 |
I think I have found a workaround on this. I create a "trigger job" that just listens for changes on the repo I want to trigger on, then create a downstream build job with multi SCM. It seems to work ok in this scenario, but I'm not really sure why. |
+1 |
We simply stopped using multiple SCM plugin, and use the shell to clone any additional repos we may need. This doesn't scale to all use cases of course as you lose out on other SCM features of Jenkins. |
I need to use this pull-request plugin in a job where 2 repos need to be checked-out:
I'm using multiple SCM plugin with 2 git scm. And as usual, I set the
Advanced/refspec
of the main project to be+refs/pull/*:refs/remotes/origin/pr/*
and leave the auxiliary project's configs intact (so jenkins should always checks out its default branch).The pull request triggers correctly the job build but the problem is that when checking out the auxiliary project, instead of the default branch, jenkins tries to checks out a pull-request branch as if it's the main project.
So from above log, jenkins tries to get
origin/pr/439/merge^{commit}
of the auxiliary project, but that doesn't exists, and I've never configures it to do that. It should always checks out the default branch of the auxiliary project.So is it a bug? Or simply because multiple scm plugin is not supported? If the latter one is true can you guys gives me some pointers so that I can try to make a contribution?
Thanks.
The text was updated successfully, but these errors were encountered: