Strider-CD/strider-status-report — pull request #1 by Frost (2014-09-04 07:53:40+00:00)
Title: Get actual job status

Unfortunately, the `test_exitcode` isn't the only thing to look for when determining the current status of a project.

One problem with this, is that `npm test` will exit with code 0 regardless if any tests fail. It will exit with a non-zero code only if the test crashed. Using `mocha` directly would solve that problem, but seing as Strider defaults node apps to running `npm test`, it would be better if this plugin reported data that was actually usable. Therefore I changed the output so it also includes the plugin_data output.

Furthermore, the existing implementation actually overwrites the values of each branch, so that if you have two projects that both have their master branch tested in Strider, the output from the status report will be the last Job (regardless of project) that was run on a master branch, and that gets repeated for every project.

I rewrote the plugin using a map/reduce solution instead, making sure that it outputs the correct data.