CI results searching via automation or...

[Trott]

See discussion at https://github.com/nodejs/testing/blob/master/doc/wg-meetings/2016-01-15.md#ci-history

/cc @nodejs/build

[Trott]

Additional comments:

• add meeting minutes #4 (comment)
• add meeting minutes #4 (comment)
• add meeting minutes #4 (comment)

[santigimeno]

I have implemented a very basic proof of concept here: https://github.com/santigimeno/ci-test-results. For the moment it just retrieves the failing tests of a specific job run, but it could easily expanded to check for a range of runs. It still has no tests, no error checking, etc. It's just to know if this fits with what @Trott had in mind

[Trott]

I'm not sure I was the one who suggested this. (Maybe, but it might have been someone else.) Anyway, looks like a fine start to me. I've submitted a pull request to arrange it in a way that I think will be more maintainable and testable, but feel free to reject the PR and do something else if you have different ideas.

EDIT: Looks like the suggestion came out of conversation between me and João. Regardless, thanks for the proof-of-concept!!!

[Trott]

/cc @nodejs/build

[santigimeno]

I've found this: https://wiki.jenkins-ci.org/display/JENKINS/Test+Results+Analyzer+Plugin. Maybe it's worth giving it a try.

[santigimeno]

This issue may be related: nodejs/build#345

[joaocgreis]

Just found this: https://www.npmjs.com/package/nodejs-ci-ctl