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

Job Config History plugin should not call User.current() during startup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • jobconfighistory-plugin
    • None
    • 2.138.2

    Description

      2.138.2 backported JEP-214/Uplink telemetry, and with it, an extension that calls save from its constructor.

      When Job Config History is installed, that results in the following warning being logged on the first startup during the save call:

      https://gist.github.com/daniel-beck/140e11878479d5c2eef882f54c4ed33d

      It's not obviously a bad idea to call save there (IMO), but there probably should be a check in JCH to not do elaborate processing during startup. Unsure.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-54888 Gearman Plugin should not access extensions from SaveableListener during startup

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-55361 DescriptorExtensionList not locking correctly, leading to deadlocks

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-58993 Jenkins allows Jenkins.save() to be called during startup

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              stefanbrausch Stefan Brausch
              danielbeck Daniel Beck
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: