Quick share of something I'm looking at based on discussions we had last week. I did some experimenting with a logstash+redis+elasticsearch setup last night, and as of this morning, I also have the latest jenkins scripts running on a local machine, running touch_ro jobs, and logging there. If you're interested to see what it looks like (very barebones setup right now) go to: http://paullarson.net:9292
All that's getting logged here is the console messages from the jenkins jobs. I could see this being pretty useful in cases where we find an odd error message and want to know how common it is. Right now, we try to spot stuff like that and log it by hand in a spreadsheet. This is very time consuming, error prone, and highly likely to miss things that we just don't know we care about *yet*. If you want a quick example, have it search for "Failed to fetch" (yes, it's case sensitive) and you can also turn on things at the bottom like job, message, etc. to see details. This will show you some previous failed builds today where I was able to reproduce some networking problems after provisioning, which I'm talking about on irc now. -Paul Larson
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
