Unstable Build Support

[emaxsaun]

Hi all, thanks again for this great plugin. I have my reporting working well now, but I always keep coming back with another issue :) But I think this is the last one!

Currently in Jenkins in our current testing framework (Cucumber-JVM, which we are trying to move off of, we mark a build as Success if is passes with one report, a Failure if both the first run and the rerun reports fail, and an Unstable if the first run report Fails, but the Rerun passes.

In Protractor, using Protractor-Retry, is there a way that you guys can send the proper exit code so that Jenkins will trigger Unstable for us in this case? Currently the tests will mark a build as Success even if the first run failed, but the second run passed. I want to have it mark as Unstable in this case to increase visibility to our team as to what the flakey tests in our suite are :) Thank you all!

[dreuxl]

hi,

we support only success (return 0) and failure (return 1), we currently dont have intermediate status code atm.

[emaxsaun]

Ah, I see. Too bad :(

This feature is really more of a nice to have for us.

I wanted to see if at some point during the test run that there was a return of 1, but at the end, if there is a return of 0, then it failed at one point, but passed on the retry, so make the build status unstable.

Maybe I will have to look into a plugin for Jenkins to force the build status to unstable for something like this.

[dreuxl]

but it s a good idea though :) let me think about it

[emaxsaun]

Ok, thanks :)

[emaxsaun]

Let me know what you think of this idea :) Maybe it can be a configuration option?