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

Show actual administrative monitor value in "Administrative monitors configuration"

    XMLWordPrintable

Details

    Description

      It would be most helpful if under the "Configure | Administrative monitors configuration" section, the actual monitor value were displayed on the page, along with the Text descriptor.

      ie:

      [  ] Deprecated Plugin Monitor  (hudson.PluginManager$PluginDeprecationMonitor )
      [  ] Missing Verification Strategy Monitor ( hudson.plugins.sshslaves.verifiers.MissingVerificationStrategyAdministrativeMonitor )

      timja's proposed workaround in How to configure administrative monitors? #774

      Best to configure it in the UI and then export it, there's a lot of different possible values

      works, but is cumbersome, not friendly and then requires user configuration changes, which breaks the Configuration as Code model

      Displaying the values in the UI would make it easier to mange those within JCasC.

      Similarly, "JENKINS-60603 - Send emails when new administrative monitors appear"m, should show both the Test descriptor and the actual value in the message.

       

      Attachments

        Issue Links

          Activity

            danielbeck Daniel Beck added a comment -

            I do not think we should expose such internals this way to support a fairly narrow, specific use case. I will object to any such pull request.

            We don't show hudson.model.FreeStyleProject anywhere either; and we're certainly never going to show the class name of the "Static Agent" anywhere on the UI.

            There are very easy ways to obtain a list of all known admin monitors through the script console; CasC should just document those.

            danielbeck Daniel Beck added a comment - I do not think we should expose such internals this way to support a fairly narrow, specific use case. I will object to any such pull request. We don't show hudson.model.FreeStyleProject anywhere either; and we're certainly never going to show the class name of the "Static Agent" anywhere on the UI. There are very easy ways to obtain a list of all known admin monitors through the script console; CasC should just document those.

            People

              Unassigned Unassigned
              ianw Ian Williams
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: