Fix for issue #37

[ramirost]

This PR fixes the issue #37 that can be reproduced when a job does not run the deploy phase.

[oliversalzburg]

Would be nice if anyone could confirm this.

[ramirost]

Of course is better if anybody else having the issue can test this but I can provide also more information to understand the fix.

When the a job is run without executing the deploy the phase object is something like this

The old code was checking always exitCode for deploy phase event when it was not executed and in such case exitCode was -1. The proposed fix only checks exitCode for deploy phase when finished is not null

[oliversalzburg]

Alright. I'll merge this, but I can't npm publish as I lack the permissions :P

[ramirost]

Thanks, for us is ok if is included in the next release as we have version 1.4.2 patched locally.

[knownasilya]

@oliversalzburg I added you to npm for this one as well 👍

[knownasilya]

I added you to all the strider related repos I have access to, including gitane and dirkeeper.

[xyb]

@knownasilya, @oliversalzburg, maybe it's time to release new version?

[oliversalzburg]

Hmm, I just published 1.4.3. @knownasilya do we have a wiki article somewhere that describes the release process (we should)?