Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
Fedora release 20 (Heisenbug) x86_64
OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00
Jenkins ver. 1.591
git plugin 2.3
multiple-scms plugin 0.3
Description
If Multiple SCMs is choosen in the Source-Code-Management section it is not possible to select a Repository Browser. The only option is (Auto).
If Git is choosen the selection works well.
Attachments
Issue Links
- is related to
-
-
- Resolved
-
Activity
David D
added a comment - well, it is not "Crashes, loss of data, severe memory leak.", but it is "critical" to our CI workflow...
it will be nice if could be fixed soon... the plug-in works well though...
if should not be tagged as critical, feel free, change it back...
thanks... David
David D
added a comment - well, it is not "Crashes, loss of data, severe memory leak.", but it is "critical" to our CI workflow...
it will be nice if could be fixed soon... the plug-in works well though...
if should not be tagged as critical, feel free, change it back...
thanks... David 
Nora Mate
added a comment - IT IS CRITICAL. I cannot imagine using Jenkins without a chance to browsing changes... can you?
After having spent 2-3 hours figuring out that this is not working, I decided not using this plugin at all and use MultiJob instead, with separate subjob to checkout each repo separately. I do not have any better idea. This plugin in this form is useless.
And why it is taking 2-3 hours to find out that something is not working: because it has its UI fully enabled, so it did not even occur to me that there is such a limitation.
PLEASE: either fix it ASAP
OR at least disable the source browsing UI elements WITH a tooltip saying not yet implemented.
Nora Mate
added a comment - IT IS CRITICAL . I cannot imagine using Jenkins without a chance to browsing changes... can you?
After having spent 2-3 hours figuring out that this is not working, I decided not using this plugin at all and use MultiJob instead, with separate subjob to checkout each repo separately. I do not have any better idea. This plugin in this form is useless.
And why it is taking 2-3 hours to find out that something is not working: because it has its UI fully enabled, so it did not even occur to me that there is such a limitation.
PLEASE: either fix it ASAP
OR at least disable the source browsing UI elements WITH a tooltip saying not yet implemented . I cannot imagine using Jenkins without a chance to browsing changes... can you?
Sounds like a major loss of functionality, which is what Major is for. See the help page accessible from the Edit Issue form. The frequent misuse of these levels (nobody wants the issue they're experiencing classified as a Minor inconvenience when it messes up their day by requiring stupid workarounds) leads to inflation and in the end everything is Critical or Blocker, rendering this classification completely useless and impossible to tell the really critical things (like data loss) from the rest. But feel free to contribute to that.
hope this can be fixed soon.