-
Bug
-
Resolution: Fixed
-
Major
-
None
When placing Subversion under multi-SCM, the selection box for "Repository Browser" is empty, instead of allowing for configurations like Fisheye, WebSVN, etc. This takes away a lot of possiblities to integrate into other systems.
- is related to
-
-
- Open
-
[JENKINS-10008] Multi-SCM break Subversion "Repository browser" section
giuliano carlini
added a comment - Offer made on freedomsponsors to fix this: http://www.freedomsponsors.org/core/issue/240/multi-scm-break-subversion-repository-browser-section). Others should feel free to add to this offer ...
giuliano carlini
added a comment - Offer made on freedomsponsors to fix this: http://www.freedomsponsors.org/core/issue/240/multi-scm-break-subversion-repository-browser-section ). Others should feel free to add to this offer ... 
Ed Burnette
added a comment - This is a very annoying, long standing problem. Each of our builds pulls code from half a dozen repositories, and when an SCM change causes a build we can only see the user and filenames, not the actual changes.
Ed Burnette
added a comment - This is a very annoying, long standing problem. Each of our builds pulls code from half a dozen repositories, and when an SCM change causes a build we can only see the user and filenames, not the actual changes. 
Jon Hermansen
added a comment - Anyone know if there is a workaround for this? Even if I have to manually edit the job file, it's better than not having the URLs...
Jon Hermansen
added a comment - Anyone know if there is a workaround for this? Even if I have to manually edit the job file, it's better than not having the URLs... Please test from Jenkins 1.586 and up whether the change in core resolves this. A short test on the development version indicates the data does not get saves correctly, but maybe I'm doing it wrong.
LuFrija
added a comment - this appears to be still broken in Jenkins 1.596.2. Switching to multiple SCM results in no choices in the "repository browser" drop-down.
LuFrija
added a comment - this appears to be still broken in Jenkins 1.596.2. Switching to multiple SCM results in no choices in the "repository browser" drop-down. LuFrija
added a comment - nevermind, the problem is on GIT, not subversion 
Russell Gallop
added a comment - This doesn't appear to be completely fixed (jenkins 1.642.1/multiple-scms 0.5).
When I first enable Multiple SCMs and add a SVN and/or Git SCM then the drop down list is populated. If I leave the configure page and return then the list just shows Auto (maybe that is the same as Daniel Beck was saying above).
Russell Gallop
added a comment - This doesn't appear to be completely fixed (jenkins 1.642.1/multiple-scms 0.5).
When I first enable Multiple SCMs and add a SVN and/or Git SCM then the drop down list is populated. If I leave the configure page and return then the list just shows Auto (maybe that is the same as Daniel Beck was saying above ). 
Lars Hupel
added a comment - Problem appears to persist with Jenkins 1.642.1. Even if I manually edit the job definition and restart Jenkins, the setting gets ignored.
Lars Hupel
added a comment - Problem appears to persist with Jenkins 1.642.1. Even if I manually edit the job definition and restart Jenkins, the setting gets ignored. 
Unfortunately, due to how the repository browsers are implemented in the core, this problem is very hard to fix. There aren't enough API extension points to allow the Multiple SCM plugin to redirect repository browser requests to the 'real' SCM plugins.