• 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.

          [JENKINS-73777] Builds: use configured TZ

          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

          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

          Rafal Kedziorski added a comment - - edited

          mawinter69 I mean TZ.

          The Locale Plugin was already installed on my Jenkins.

          In Jenkins I see

          And my Chrome is set to German:

          But why is my Jenkins in english? Wondering.

          I saved it again and now it's german.

          Rafal Kedziorski added a comment - - edited mawinter69 I mean TZ. The Locale Plugin was already installed on my Jenkins. In Jenkins I see And my Chrome is set to German: But why is my Jenkins in english? Wondering. I saved it again and now it's german.

          And after it "switched" to german it looks good.

          But why was the saved german ignored?

          And if I go back to english ...

          Rafal Kedziorski added a comment - And after it "switched" to german it looks good. But why was the saved german ignored? And if I go back to english ...

          mawinter69 why is this closed, when this is different?

          Rafal Kedziorski added a comment - mawinter69 why is this closed, when this is different?

          Markus Winter added a comment -

          You opened this ticket originally because you thought that the build history widget has a problem, but it turned out it hasn't.

          I would prefer that a new issue is opened specifically claiming that the stage view plugin is not respecting timezone and locale. 

          Markus Winter added a comment - You opened this ticket originally because you thought that the build history widget has a problem, but it turned out it hasn't. I would prefer that a new issue is opened specifically claiming that the stage view plugin is not respecting timezone and locale. 

          I was not sure which component has the problem. I'll create a new ticket in a few days. Thx.

          Rafal Kedziorski added a comment - I was not sure which component has the problem. I'll create a new ticket in a few days. Thx.

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

              Created:
              Updated:
              Resolved: