[LRUG] scrolling through long testing logs to find errors from CI on PRs

[Jon Rowe]

The “bring your own compute” CI provider Buildkite [1] has a feature called annotations. Which allows you to bring failure messages up to outside of the logs.

They have a plugin that does this automatically for RSpec [2].

It’s pretty great!

The technique used though, a custom formatter, could easily be extended to comment on PRs with a bit of wiring.

Cheers
Jon Rowe

[1] buildkite.com (https://buildkite.com/)
[2] github.com/sj26/rspec-buildkite (https://github.com/sj26/rspec-buildkite)

Jon Rowe
---------------------------
mail at jonrowe.co.uk
jonrowe.co.uk

On 27 February 2019 at 09:58, Samuel Joseph wrote:
> Hi LRugers,
>
> Hope everyone is well. I was wondering if anyone else found themselves
> getting exhausted scrolling through long testing logs to find errors
> from CI on PRs? All the CI systems we've used so far are great at
> providing a link to the complete CI output in a PR, but it always seems
> to take a fair few minutes to get through the CI logs to find the actual
> error message that will then allow us to debug the issue.
>
> Does anyone know of a clever CI system that is smart enough to rake the
> relevant error message (from the few failing tests) and post that
> directly into a GitHub PR or similar in order to speed up the process of
> analysis?
>
> Many thanks in advance
>
> Best, Sam
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org (mailto:Chat at lists.lrug.org)
> Archives: lists.lrug.org/pipermail/chat-lrug.org (http://lists.lrug.org/pipermail/chat-lrug.org)
> Manage your subscription: lists.lrug.org/options.cgi/chat-lrug.org (http://lists.lrug.org/options.cgi/chat-lrug.org)
> List info: lists.lrug.org/listinfo.cgi/chat-lrug.org (http://lists.lrug.org/listinfo.cgi/chat-lrug.org)
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20190227/4e085b3a/attachment-0001.html>