HOUR field in Build Periodically Schedule incorrectly interpretted when > 11

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When scheduling a build, the HOUR field doesn't seem to be interpretted
      correctly when it's greater than 11. For example, a schedule of 0 13 * * *
      doesn't kick off the job at 1 PM, while a schedule of 0 1 * * * does kick it off
      at 1PM, as well as at 1AM.

            Assignee:
            Unassigned
            Reporter:
            johnsol
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: