Ask Your Question
1

Build Farm Output is Difficult to Read

asked 2013-12-26 09:24:27 -0600

David Lu gravatar image

Why do I need to look through over 1000 lines of output to figure out what went wrong with the build?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
2

answered 2013-12-26 16:01:39 -0600

tfoote gravatar image

If you don't provide the full output, you may miss important things that happen during the build. If the information is not logged it is gone because you don't have access to the build environment for introspection afterwards.

When viewing a failed build I usually start by searching for "error" caps insensitively and find what the error is and work back from there. Using this technique, especially searching from the bottom it usually takes only a couple of seconds to find the failure in a log.

edit flag offensive delete link more

Comments

Great tip that I should've asked long ago. I also search `not found`.

130s gravatar image130s ( 2013-12-26 16:06:59 -0600 )edit

That is a good tip, but that doesn't alleviate the essential usability problem. I don't argue having access to the log. It's that it doesn't provide any high level information to give a hint other than reading the log. This answer seems to just be RTFM.

David Lu gravatar imageDavid Lu ( 2013-12-27 05:00:41 -0600 )edit

At the highest level you get pass or fail. If you have any suggestions for libraries or algorithms we can apply to them to give a good summary of failures we'd be happy to add them.

tfoote gravatar imagetfoote ( 2013-12-27 06:21:12 -0600 )edit

Sounds more like a good enhancement for jenkins (or there might already exist plugins) ?

130s gravatar image130s ( 2013-12-27 14:50:47 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2013-12-26 09:24:27 -0600

Seen: 53 times

Last updated: Dec 26 '13