Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325324

Summary: Improve console logging information for jobs
Product: Community Reporter: Steve Powell <zteve.powell>
Component: CI-JenkinsAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: denis.roy
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:

Description Steve Powell CLA 2010-09-15 06:01:34 EDT 
The console logs for a job have (apparently) no time-stamp information.  This is a request to enhance the output to include time-stamps for every significant output line -- this is a really useful diagnostic feature and is standard in commercial ci-servers.
Comment 1 Steve Powell CLA 2010-10-14 06:21:52 EDT 
Recent investigations into chronic job failures have highlighted the abysmal logging of jobs.  It is crucial that all the job parameters (in the job configuration and in the slave environment) should be logged with the job results for reference.

The job configuration, for example, is an xml file saved in hudson (somewhere).  This ought to be snapshot and preserved with the job console log and output.  Also, the console should record the environment at the start of the log for reference -- including the time.  All environment variables for the main process would be helpful; and other slave/job parameters (for example, the full path of the workspace, details of the machine environment and the versions of the major components used in the job (Java/Ant/Git/etc depending upon options used) need to be available.

Please add this to the time-stamping requested already.
Comment 2 Denis Roy CLA 2013-09-26 09:27:57 EDT 
Is this still applicable?
Comment 3 Denis Roy CLA 2013-10-18 16:27:58 EDT 
Closing as wontfix.