Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: timestamper-plugin
-
Labels:
-
Environment:Pipeline Job 2.26, Timestamper 1.8.10, Jenkins 2.138.2 LTS, Windows Server 2016 master and agents
-
Similar Issues:
-
Released As:1.9
Description
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.
Attachments
Issue Links
- is related to
-
JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1
-
- Open
-
- relates to
-
JENKINS-48344 Log files generated by Jenkins pipeline scripts are bloated
-
- Resolved
-
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
-
JENKINS-52165 Use push rather than pull for durable task logging
-
- Reopened
-
-
JENKINS-54133 No ANSI coloring on slave agents in pipeline
-
- Closed
-
The result is the same, yes. But I don't think the cause was the same, in our case connection with agent is working unless some specific combinaison of components:
In our case, something occurs at the end of the job between master and slave, and master never receive the "OK" result from slave (nor the full logs). And after 9mn of inactivity build fail and agent is disconnected. It's always reproduced with hudge logs, but maybe logs size is just a factor triggering another hidden synchro/lock problem.
For now "USE_WATCHING=false" is set in our Jenkins master and is an acceptable solution for us.