-
Bug
-
Resolution: Fixed
-
Major
-
MultipleSCM
Initial description:
Usage of Perforce plugin in the set-up of multiple SCM section leads to Java exception with no explanations of failure. Seems that Perforce plugin somehow ignores "View Map" parameters in "newInstance" handler.
The real issues:
- MultipleSCMs use DataBoundConstructor instead of newInstance
- radioBlock names are not unique
- ...
[JENKINS-18583] [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
Assignee | Original: Rob Petti [ rpetti ] | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
Usage of Perforce plugin in the set-up of multiple SCM section leads to Java exception with no explanations of failure. Seems that Perforce plugin somehow ignores "View Map" parameters in "newInstance" handler. |
New:
Initial description: {quote} Usage of Perforce plugin in the set-up of multiple SCM section leads to Java exception with no explanations of failure. Seems that Perforce plugin somehow ignores "View Map" parameters in "newInstance" handler. {quote} The real issues: - MultipleSCMs use DataBoundConstructor instead of newInstance - radioBlock names are not unique - ... |
Summary | Original: [MultipleSCM integration] - "View Map" is empty in case of multiple Perforce SCM instances | New: [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs |
Are you setting up more than one PerforceSCM? Does it happen when you only set up one under MultipleSCM?