[JIRA] (JENKINS-38381) Optimize log handling

[email protected] (JIRA) Tue, 27 Sep 2016 12:14:11 -0700

Title: Message Title

Jesse Glick commented on

Basic implementation of a unified log is working. Now I am looking into having an externalizable log storage, and specifically allowing DurableTaskStep.Execution to stream log text directly there from an agent. But when the master is not involved in collecting log output from a sh/bat step, then it is pointless to have it polling the agent over Remoting every 15s or less just to get an exit status and save a log location—this just adds traffic to the channel, and load to the master. So now I am investigating whether the controller can autonomously stream output and send a callback with exit status. This is essentially a rewrite a durable task handling. The goal is that if you run, say,

 
                                                                node {
  sh '''#!/bin/bash
for x in {0000..9999}
do
  echo $x
  sleep 1
done
'''
}
 
                                                            

then for the next three hours there should be zero activity on the remoting channel (other than ping threads) and zero load on master related to this build (assuming no human is watching the log).

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38381) Optimize log handling

Reply via email to