• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • support-core-plugin
    • None

      We should record some information about the folder that the plugins were extracted to. Currently the md5 values of the plugins are recorded, but no information relating to the extraction is recorded. This can sometimes be the cause of Jenkins failing to start.

          [JENKINS-26615] Record plugin folder corrupt information

          +1, definitely. That would be much valuable. For example, we recently had a case, where we think the WEB-INF/lib/classes.jar uncompressed part of the openid plugin was corrupted.

          With that additional information, we would have been immediately able to check its checksum against the expected one for the plugin version (information we do have) and see if that could be the culprit, and be quicker to resolve the issue.

          Baptiste Mathus added a comment - +1, definitely. That would be much valuable. For example, we recently had a case, where we think the WEB-INF/lib/classes.jar uncompressed part of the openid plugin was corrupted. With that additional information, we would have been immediately able to check its checksum against the expected one for the plugin version (information we do have) and see if that could be the culprit, and be quicker to resolve the issue.

          Baptiste Mathus added a comment - - edited

          Also, this is probably to be discussed: but I think it would be valuable information AND not that costly to generate the checksum of the whole JENKINS_HOME.

          Maybe we could/should just exclude the jobs/ directory by default. But I don't see why another directory would grow to more than a few hundreds quite small files.

          And anyway, this is something the plugin could warn the user of. Say uncheck some options by default if a pre-analysis shows the number of files is too big (or the size).

          Baptiste Mathus added a comment - - edited Also, this is probably to be discussed: but I think it would be valuable information AND not that costly to generate the checksum of the whole JENKINS_HOME. Maybe we could/should just exclude the jobs/ directory by default. But I don't see why another directory would grow to more than a few hundreds quite small files. And anyway, this is something the plugin could warn the user of. Say uncheck some options by default if a pre-analysis shows the number of files is too big (or the size).

            schristou Steven Christou
            schristou Steven Christou
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: