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

time rules uses different time-stamp from build start

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • clearcase-plugin
    • None
    • ClearCase plugin 1.3.6

      With the option "Use time rule in config spec" the time rule added at the beguinning of config spec uses a different timestamp from the reference start of the build and with one hour difference.

      Example for some build

      • Build #14 (Sep 30, 2011 2:29:27 AM)
      • env: BUILD_ID=2011-09-30_02-29-27
      • CC time: time 30-sep-11.01:29:53utc+0000

      So both the time displayed in Jenkins and the environment variable created during the job use the same time stamp, but what is used in the ClearCase time rule seems to be one hour earlier and slightly different seconds after the build start.

      The timestamp used in the time rule should be exactly the same as used in build itself.

      We have our unix server set to use TZ=Europe/Lisbon (both jenkins server and Vob server use same TZ, and sync with NTP with same clock source), if it helps in your analysis.

            vlatombe Vincent Latombe
            josesa Jose Sa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: