-
Bug
-
Resolution: Unresolved
-
Major
I configured job with multiscm plugin and used same github project but with different branches.
But branch for second project is not correctly identified because BuildData object is not correctly returned here:
public @CheckForNull BuildData getBuildData(Run build) { BuildData buildData = null; while (build != null) { List<BuildData> buildDataList = build.getActions(BuildData.class); for (BuildData bd : buildDataList) { if (bd != null && isRelevantBuildData(bd)) { buildData = bd; break; } } if (buildData != null) { break; } build = build.getPreviousBuild(); } return buildData; }
Guilty method is
isRelevantBuildData as under the hood it checks like this:
return remoteUrls.contains(remoteUrl);
and it doesn't honour branch name.
So I think the proper fix is to add somehow branch name here.
Is there a compelling reason why you're continuing to use the multi-scm plugin (with all of the challenges associated with that plugin) when the Pipeline plugins have much better support for operations with multiple repositories and multiple branches within a repository?
In general, I am not investigating or fixing issues in the git plugin which are related to the multi-scm plugin.