Avoid stack trace in logs when usage stats can not be sent

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • jenkins-2.304 and 2.303.1

      The usage statistics are sent ciphering the data. Under certain configuration of the JVM with some security providers, the sending could fail ending up in a stack trace printed in the logs. It happens every day.

      This ticket is to lower the level of the stack trace printed to avoid too much noise and keep just an INFO message in the log. The instance is not compromised so it's better INFO than WARNING.

            Assignee:
            Ramon Leon
            Reporter:
            Ramon Leon
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: