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

A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • None
    • 1.5 version of the plugin

      Once the plugin is installed if we add an option that is not valid from "Manage Jenkins" -> "Open File Handle" and submit, the Jenkins instance is killed (it does a System.exit(-1))

       

      For example, if you test adding the option: "test", the instance is killed automatically

          [JENKINS-53394] A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance

          Ramon Leon added a comment -

          Add the final PR after discussion

          Ramon Leon added a comment - Add the final PR after discussion

          Ramon Leon added a comment -

          the PR #41 in the plugin (file-leak-detector-plugin). It's blocked by the PR #5 in the library (file-leak-detector)

          Ramon Leon added a comment - the PR #41 in the plugin (file-leak-detector-plugin). It's blocked by the PR #5 in the library (file-leak-detector)

          Ramon Leon added a comment - Two previous PRs for discussion: https://github.com/kohsuke/file-leak-detector/pull/39 https://github.com/kohsuke/file-leak-detector/pull/40 Finally we agree to: https://github.com/kohsuke/file-leak-detector/pull/41 https://github.com/jenkinsci/file-leak-detector-plugin/pull/5

          Ramon Leon added a comment -

          Released the version 1.6 of file-leak-detector plugin. Changelog:

          https://wiki.jenkins.io/display/JENKINS/File+Leak+Detector+Plugin

          Ramon Leon added a comment - Released the version 1.6 of file-leak-detector plugin. Changelog: https://wiki.jenkins.io/display/JENKINS/File+Leak+Detector+Plugin

            mramonleon Ramon Leon
            jraezrus Javier Raez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: