Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25787

Repository Browser broken with Multiple SCMs plugin

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • multiple-scms-plugin
    • 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

      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.

          [JENKINS-25787] Repository Browser broken with Multiple SCMs plugin

          Daniel Beck added a comment -

          From https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin section "Limitations":

          Repository browser configuration is also not supported in the current version.

          Looks like the Multiple SCMs authors consider this a bug in their plugin.

          Daniel Beck added a comment - From https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin section "Limitations": Repository browser configuration is also not supported in the current version. Looks like the Multiple SCMs authors consider this a bug in their plugin.

          Steffen Sledz added a comment -

          What a pity.

          Steffen Sledz added a comment - What a pity.

          LuFrija added a comment -

          Actually it seems there is a partial support: in fact when a subversion repo is added in the multi-scm, the repo browsers are available. However when a git repo si selected then the list is empty.

          LuFrija added a comment - Actually it seems there is a partial support: in fact when a subversion repo is added in the multi-scm, the repo browsers are available. However when a git repo si selected then the list is empty.

          Any chance it will be fixed soon?

          Tomasz Lisowski added a comment - Any chance it will be fixed soon?

          David D added a comment -

          hope this can be fixed soon.

          David D added a comment - hope this can be fixed soon.

          Daniel Beck added a comment -

          Critical
          Crashes, loss of data, severe memory leak.

          Very funny.

          Daniel Beck added a comment - Critical Crashes, loss of data, severe memory leak. Very funny.

          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 .

          Daniel Beck added a comment -

          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.

          Daniel Beck added a comment - 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.

            kbell Kevin Bell
            sledz Steffen Sledz
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: