Currently if you want to manage tool installations in a Jenkins instance, you just go to the master /configure page. Unfortunately this can get out of hand: when there are a lot of tools already (such as twenty dot-dot JDK releases), regular Jenkins configuration can get lost in the mess.

      The configureTools branch (see URL) proposes to split tool installations off into their own configuration page for comfort.

      Open issues:

      1. All tools are shown on a single page, though it may also be feasible to produce one page per tool type (Ant, Maven, JDK, ...); or one page with tabs, if there were a clear meaning for Save and Apply in that case.
      2. The management link uses the same setting.png as the main /configure page; probably needs its own icon.
      3. TBD whether other bits of configuration belong in the new location, notably ToolLocationNodeProperty and Shell.DescriptorImpl - should there be a way of indicating that a given Descriptor would like to be rendered on an alternate config page?

          [JENKINS-14538] Separate "configure tools" page

          Jesse Glick created issue -

          jan_ruzicka added a comment -

          This is interesting idea.
          Can there be a link from the main configuration page to the one with separated plugin settings?
          It would be nice for easier transition.

          jan_ruzicka added a comment - This is interesting idea. Can there be a link from the main configuration page to the one with separated plugin settings? It would be nice for easier transition.

          Jesse Glick added a comment -

          I committed a different UI to the branch, a much less disruptive change from the current UI: all tools still shown in /configure, but collapsed by default, with Advanced-style buttons labeled e.g. "Ant installations...". Working except for button alignment which is gratuitously indented.

          Jesse Glick added a comment - I committed a different UI to the branch, a much less disruptive change from the current UI: all tools still shown in /configure , but collapsed by default, with Advanced-style buttons labeled e.g. "Ant installations...". Working except for button alignment which is gratuitously indented.
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          http://jenkins-ci.org/commit/jenkins/03546bd62c2abf14130efdc2739a17a3da978974
          Log:
          [FIXED JENKINS-14538] Collapse nonempty tool installation sections by default in /configure.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/03546bd62c2abf14130efdc2739a17a3da978974 Log: [FIXED JENKINS-14538] Collapse nonempty tool installation sections by default in /configure.
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          URL Original: https://github.com/jenkinsci/jenkins/compare/master...configureTools New: https://github.com/jenkinsci/jenkins/commit/468c5210355d41020ba168cfe45e2b4ef128ccc1
          Description Original: Currently if you want to manage tool installations in a Jenkins instance, you just go to the master {{/configure}} page. Unfortunately this can get out of hand: when there are a lot of tools already (such as twenty dot-dot JDK releases), regular Jenkins configuration can get lost in the mess.

          The {{configureTools}} branch (see URL) proposes to split tool installations off into their own configuration page for comfort.

          Open issues:
          # All tools are shown on a single page, though it may also be feasible to produce one page per tool type (Ant, Maven, JDK, ...); or one page with tabs, if there were a clear meaning for Save and Apply in that case.
          # The management link uses the same {{setting.png}} as the main {{/configure}} page; probably needs its own icon.
          # TBD whether other bits of configuration belong in the new location, notably {{ToolLocationNodeProperty}} and {{Shell.DescriptorImpl}} - should there be a way of indicating that a given {{Descriptor}} would like to be renderer on an alternate config page?
          New: Currently if you want to manage tool installations in a Jenkins instance, you just go to the master {{/configure}} page. Unfortunately this can get out of hand: when there are a lot of tools already (such as twenty dot-dot JDK releases), regular Jenkins configuration can get lost in the mess.

          The {{configureTools}} branch (see URL) proposes to split tool installations off into their own configuration page for comfort.

          Open issues:
          # All tools are shown on a single page, though it may also be feasible to produce one page per tool type (Ant, Maven, JDK, ...); or one page with tabs, if there were a clear meaning for Save and Apply in that case.
          # The management link uses the same {{setting.png}} as the main {{/configure}} page; probably needs its own icon.
          # TBD whether other bits of configuration belong in the new location, notably {{ToolLocationNodeProperty}} and {{Shell.DescriptorImpl}} - should there be a way of indicating that a given {{Descriptor}} would like to be rendered on an alternate config page?

          dogfood added a comment -

          Integrated in jenkins_main_trunk #1813
          [FIXED JENKINS-14538] Collapse nonempty tool installation sections by default in /configure. (Revision 03546bd62c2abf14130efdc2739a17a3da978974)

          Result = UNSTABLE
          Jesse Glick : 03546bd62c2abf14130efdc2739a17a3da978974
          Files :

          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #1813 [FIXED JENKINS-14538] Collapse nonempty tool installation sections by default in /configure. (Revision 03546bd62c2abf14130efdc2739a17a3da978974) Result = UNSTABLE Jesse Glick : 03546bd62c2abf14130efdc2739a17a3da978974 Files : changelog.html
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-4487 [ JENKINS-4487 ]

          nice change, but I would still prefer a separate page
          to global configuration is a mess on its own and dividing it into different pages would help

          Dominik Bartholdi added a comment - nice change, but I would still prefer a separate page to global configuration is a mess on its own and dividing it into different pages would help

            amuniz Antonio Muñiz
            jglick Jesse Glick
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: