[Jenkins-infra] Proposal: only keep last 24h of ci.jenkins.io access logs

R. Tyler Croy tyler at monkeypox.org
Fri Mar 17 15:33:08 UTC 2017


(replies inline)

On Fri, 17 Mar 2017, Daniel Beck wrote:

> 
> > On 16.03.2017, at 19:42, R. Tyler Croy <tyler at monkeypox.org> wrote:
> > 
> > Any compelling reason to store these logs?
> 
> Not right now, but given that I've asked for logs to investigate something repeatedly over the last year only to get the answer "logs are overrated", I wouldn't be surprised if this came up soon enough.
> 
> Same with keeping build records. Keeping 5 builds doesn't help anyone if something goes wrong and you learn about it 24 hours (50 builds) later.


Apache access logs and Apache error logs are different files. Any debugging
information would be found in the error logs. All these access logs tell us is
how many jerks are running Checkman or Catlight hitting ci.jenkins.io every
bloody second.


- R. Tyler Croy

------------------------------------------------------
     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: rtyler at jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20170317/dd86c4e5/attachment.asc>


More information about the Jenkins-infra mailing list