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

When using a 12 hour time format Jenkins will say 12:00am and 12:00pm which do not exist

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      Build history widget shows ambiguous times for noon and midnight builds when the user has a 12 hour clock format.


      There is no such time as 12:00 am or 12:00 pm.  The times are completely ambiguous as 12 is neither before the meridian nor after the meridian.

      miday should be 12:00 noon or 12:00 midnight.

      This becomes more confusing when you only have some sporadic builds and can not compare one build against another on the same day.

      This article explains this and especially the lines "most people", ie not everyone and wikipedia has a whole section on this.

      The normal way to disambiguate this is to not use am/pm, or to provide context.  but with a job that runs sporadically (less than once every 2 days, it would not be surrounded by any other job which can provide context in the same day

       

      steps to reproduce

      Create a job that runs every hour

      configure your timezone preferences in one that desire a 12 hour clock format. (e.g. and American one)

      wait a 24 hours

      go to the job page and look at the times in the build history widget

      expected result

      the time goes from 11:00pm to 12 midnight to 1:00 am

      actual results

      The time goes from 11:00pm to 12:00 am to 1:00 am

       

      Workaround

      Use a proper clock format

          [JENKINS-75171] When using a 12 hour time format Jenkins will say 12:00am and 12:00pm which do not exist

          There are no comments yet on this issue.

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: