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

Builds: use configured TZ

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • core
    • Jenkins Version 2.476

      In the current weekly Jenkins version the build table isn't using the configured TZ.

        1. image-2024-09-16-12-17-14-689.png
          image-2024-09-16-12-17-14-689.png
          15 kB
        2. image-2024-09-15-18-53-43-334.png
          image-2024-09-15-18-53-43-334.png
          96 kB
        3. image-2024-09-15-18-52-35-672.png
          image-2024-09-15-18-52-35-672.png
          86 kB
        4. image-2024-09-15-18-47-29-034.png
          image-2024-09-15-18-47-29-034.png
          23 kB
        5. image-2024-09-15-18-42-59-469.png
          image-2024-09-15-18-42-59-469.png
          4 kB
        6. image-2024-09-14-23-52-50-615.png
          image-2024-09-14-23-52-50-615.png
          126 kB

          [JENKINS-73777] Builds: use configured TZ

          Rafal Kedziorski created issue -
          Markus Winter made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: build-history-manager-plugin [ 26124 ]
          Markus Winter made changes -
          Component/s New: pipeline-stage-view-plugin [ 21139 ]
          Component/s Original: core [ 15593 ]

          Markus Winter added a comment -

          Reassigned to pipeline-stage-view plugin. The build history on the left is properly respecting the user defined TZ setting, stage-view plugin always uses the TZ of the controller.

          Markus Winter added a comment - Reassigned to pipeline-stage-view plugin. The build history on the left is properly respecting the user defined TZ setting, stage-view plugin always uses the TZ of the controller.

          Markus Winter added a comment - - edited

          But maybe you mean more the locale thing, build history seems to be always using a 12h format with AM/PM, while stage view uses a 24h format

          Markus Winter added a comment - - edited But maybe you mean more the locale thing, build history seems to be always using a 12h format with AM/PM , while stage view uses a 24h format
          Markus Winter made changes -
          Assignee Original: Damian Szczepanik [ dszczepanik ] New: Sam Van Oort [ svanoort ]

          Rafal Kedziorski added a comment -

          mawinter69 you're right. I mean the format.

          Rafal Kedziorski added a comment - mawinter69 you're right. I mean the format.

          Markus Winter added a comment -

          Just checked again, the build history widget respects the locale setting of the browser, switching to german displays the timestamps in 24h format, using english I get 12h format with AM/PM. The widget also respects the user configured timezone.
          Also before the re-design of the widget, it was properly making use of the browser locale and the user defined timezone

          Markus Winter added a comment - Just checked again, the build history widget respects the locale setting of the browser, switching to german displays the timestamps in 24h format, using english I get 12h format with AM/PM. The widget also respects the user configured timezone. Also before the re-design of the widget, it was properly making use of the browser locale and the user defined timezone

          Rafal Kedziorski added a comment - - edited

          The screenshot was made with Chrome and German setting.

          TZ is set to:

          [Service]
# Add JVM configuration options
Environment="JAVA_OPTS=-Djava.awt.headless=true -Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=30 -Duser.timezone=Europe/Berlin"

          Rafal Kedziorski added a comment - - edited The screenshot was made with Chrome and German setting. TZ is set to: [Service] # Add JVM configuration options Environment= "JAVA_OPTS=-Djava.awt.headless= true -Dcom.cloudbees.workflow. rest .external.JobExt.maxRunsPerJob=30 -Duser.timezone=Europe/Berlin"

          Markus Winter added a comment -

          "-Duser.timezone=Europe/Berlin" This is not setting any locale, this just sets the timezone.

          And it seems your browser is not set to german, otherwise it should say "Jetzt bauen" and not "Build now".

          There is the https://plugins.jenkins.io/locale/ plugin that can force the locale

          Markus Winter added a comment - "-Duser.timezone=Europe/Berlin" This is not setting any locale, this just sets the timezone. And it seems your browser is not set to german, otherwise it should say "Jetzt bauen" and not "Build now". There is the https://plugins.jenkins.io/locale/ plugin that can force the locale

            Unassigned Unassigned
            oicfar Rafal Kedziorski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: