https://github.com/jenkinsci/jenkins/pull/4734

      Jenkins does not log script console activity. This pull request implements logging in the following format:

      IP|username|Activity Type (in this case, "ScriptConsole")|Additional context (in this case, Base64 of the script executing).

      Log severity is set to INFO. This is the lowest severity that is still shown in the logs without setting up custom listeners. This is by design, so that all Jenkins installs will have this log without having to modify the installation.

      The log fields are split by the pipe character for easy parsing, and the script contents are Base64 encoded to ensure the log is in a single line of text.

          [JENKINS-62397] ScriptConsole activity is not logged

          Kaue Pena created issue -
          Kaue Pena made changes -
          Description Original: Jenkins does not log script console activity. This pull request implements logging in the following format:

          !image-2020-05-21-13-08-17-695.png!

          IP|username|Activity Type (in this case, "ScriptConsole")|Additional context (in this case, Base64 of the script executing).

          Log severity is set to INFO. This is the lowest severity that is still shown in the logs without setting up custom listeners. This is by design, so that all Jenkins installs will have this log without having to modify the installation.

          The log fields are split by the pipe character for easy parsing, and the script contents are Base64 encoded to ensure the log is in a single line of text.
          New: https://github.com/jenkinsci/jenkins/pull/4734

          Jenkins does not log script console activity. This pull request implements logging in the following format:

          !image-2020-05-21-13-08-17-695.png!

          IP|username|Activity Type (in this case, "ScriptConsole")|Additional context (in this case, Base64 of the script executing).

          Log severity is set to INFO. This is the lowest severity that is still shown in the logs without setting up custom listeners. This is by design, so that all Jenkins installs will have this log without having to modify the installation.

          The log fields are split by the pipe character for easy parsing, and the script contents are Base64 encoded to ensure the log is in a single line of text.
          Kaue Pena made changes -
          Labels Original: logging script security New: logging lts-candidate script security
          Daniel Beck made changes -
          Link New: This issue duplicates JENKINS-41516 [ JENKINS-41516 ]
          Daniel Beck made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Daniel Beck made changes -
          Labels Original: logging lts-candidate script security New: logging script security

            paloaltonetworks_kpena Kaue Pena
            paloaltonetworks_kpena Kaue Pena
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: