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

Timestamps missing for agent-based steps in Pipeline Job 2.26

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • timestamper-plugin
    • Pipeline Job 2.26, Timestamper 1.8.10, Jenkins 2.138.2 LTS, Windows Server 2016 master and agents
    • 1.9

      After upgrading to Pipeline Job 2.26 earlier today, in the Console Log for pipeline builds, I only appear to have timestamps for the operations performed by the master node (i.e., the initial git checkout), but all remaining build steps that are performed on agent nodes lack timestamps entirely. The job properly recognizes that timestamps were enabled in the first place, so provides the typical "System clock time" vs., "Elapsed time" options on the left, but these only have an effect for the master node-occurring timestamps; timestamps for steps taking place on agent nodes are missing regardless.

          [JENKINS-54081] Timestamps missing for agent-based steps in Pipeline Job 2.26

          Nick Jones created issue -
          Vivek Pandey made changes -
          Assignee New: Jesse Glick [ jglick ]

          Vivek Pandey added a comment -

          jglick another possible regression or this change in functionality is intentional? Looks like legit complain to me. PTAL.

          Vivek Pandey added a comment - jglick another possible regression or this change in functionality is intentional? Looks like legit complain to me. PTAL.

          Nick Jones added a comment -

          I would hope it’s not intended; all our builds occur on agents (not the master) and — in case this is a factor — must run on Windows due to our tooling (e.g., Visual Studio). Running builds on the master or on non-Windows agents would not be an option for us. Thanks for looking into it!

          Nick Jones added a comment - I would hope it’s not intended; all our builds occur on agents (not the master) and — in case this is a factor — must run on Windows due to our tooling (e.g., Visual Studio). Running builds on the master or on non-Windows agents would not be an option for us. Thanks for looking into it!

          Vivek Pandey added a comment -

          medianick Right, most users run their builds on agent so its probably a regression.

          Vivek Pandey added a comment - medianick Right, most users run their builds on agent so its probably a regression.
          Jesse Glick made changes -
          Labels New: regression

          Jesse Glick added a comment -

          Logs are now generated on the agent where applicable. I am not sure offhand why this would break the timestamper plugin, though. Do you have a sample Jenkinsfile? Anyway please note that the proposed JENKINS-48344 would make timestamp usage from Jenkins much more efficient (and it is tested with agent-based sh steps).

          Jesse Glick added a comment - Logs are now generated on the agent where applicable. I am not sure offhand why this would break the timestamper plugin, though. Do you have a sample Jenkinsfile ? Anyway please note that the proposed JENKINS-48344 would make timestamp usage from Jenkins much more efficient (and it is tested with agent-based sh steps).
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-48344 [ JENKINS-48344 ]
          Jesse Glick made changes -
          Component/s New: timestamper-plugin [ 15749 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-38381 [ JENKINS-38381 ]

            jglick Jesse Glick
            medianick Nick Jones
            Votes:
            9 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: