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

Global pipeline libraries settings UI is messed up - multiple libs overlap each other

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • pipeline, workflow-cps-global-lib-plugin
    • None
    • Jenkins ver. 2.73.2 in Chromium or Firefox
      Jenkins ver. 2.60.2 in Chromium or Firefox

      The settings block for global pipeline libraries is messed up. When you add more than one library, the blocks for the libraries will somehow overlap each other, so you only see all the settings for one library and the others are cut off. Clicking the chosen retrieval method somehow changes that but then suddenly options are visible that should be hidden due to the selected options.

      I attached two screenshots. One shows the config as it is presented directly after I opened the settings page. You can see that the settings for first library are not displayed completely. The second screenshot shows the same page after I clicked on "Modern SCM". You can see how everything moved around and settings for GitHub appeared even though GitHub is not selected.

      The issue exists in both Jenkins 2.60.2 and 2.73.2, the latter was freshly installed. Both run in Tomcat.

        1. Bildschirmfoto von »2017-10-26 22-31-49«.png
          Bildschirmfoto von »2017-10-26 22-31-49«.png
          120 kB
        2. Bildschirmfoto von »2017-10-26 22-31-56«.png
          Bildschirmfoto von »2017-10-26 22-31-56«.png
          101 kB

          [JENKINS-47677] Global pipeline libraries settings UI is messed up - multiple libs overlap each other

          Joachim Durchholz added a comment - - edited

          Confirming: I have the exact same problem.

          Webtools showed me that the input fields are there, including the missing settings, but they are made invisible via CSS.

          Selecting an already-selected radio button in the SCM area would make many (possibly all) fields visible. Clicking another radio button would change the layout, possibly because some page elements would still toggle the visibility of some elements.

          My best bet is that some internal framework is mixing up IDs and applying visibility-changing code to the wrong page elements. Not 100% sure that the effect was limited to the SCM area, I think so but haven't validated. (I can try and run a structural comparison over the whole configuration page if so desired, provided a developer confirms that it's worth doing.)

           (UPDATE: We are using Jenkins ver. 2.89.2 in a corporate setting. If this is a solved problem, I'd like to know so I can tell the admins to upgrade.)

          Joachim Durchholz added a comment - - edited Confirming: I have the exact same problem. Webtools showed me that the input fields are there, including the missing settings, but they are made invisible via CSS. Selecting an already-selected radio button in the SCM area would make many (possibly all) fields visible. Clicking another radio button would change the layout, possibly because some page elements would still toggle the visibility of some elements. My best bet is that some internal framework is mixing up IDs and applying visibility-changing code to the wrong page elements. Not 100% sure that the effect was limited to the SCM area, I think so but haven't validated. (I can try and run a structural comparison over the whole configuration page if so desired, provided a developer confirms that it's worth doing.)  (UPDATE: We are using Jenkins ver. 2.89.2 in a corporate setting. If this is a solved problem, I'd like to know so I can tell the admins to upgrade.)

            Unassigned Unassigned
            konzertheld Christian Gredig
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: