Controller JVM Timezone versus Agent Local Time for Jenkins Build Timestamps

Timestamp Source for Cross-Region Jenkins Builds

Jenkins stores build timestamps in UTC on the controller, and Pipeline steps read that controller clock through currentBuild. Console output, however, can reflect the system time of the agent that executed the step. When agents run in different time zones, console entries may appear out of order relative to build history.

The goal is one consistent timestamp reference for audit trails without changing the controller JVM timezone, which can shift how historical plugins render past builds. The unresolved choice is whether pipeline records should anchor to the controller JVM clock or preserve each agent's local wall-clock time.

Should pipeline build records use the controller JVM clock or the executing agent's local system time? Does the Build Timestamp Plugin format output from the controller clock or the agent clock? Is browser-local rendering in the Jenkins UI sufficient for cross-region audit consistency?