Simple scenario:
Freestylejob A that triggers in build step a freestylejob B.
Job B does nothing except "scan for compiler warnings" with MSBuild parser.

If you run Job B, it succeeds okay.
If you run Job A, it triggers Job B as expected, but runs forever (or until cancelled ) even if the job B is already finished successfully.

I detected this problem in a different scenario, but even this simple configuration doesn't work

As I have multiple nested jobs running and mostly MSBUILD jobs, it would be very nice if I also can use your warnings-plugin as it looks quite good.
But due to the fact that the described behaviour blocks up all nested jobs, it is quite annoying as it took me also a long time to identify this problem.
Any help is welcome and additional informations can be also provided if needed.

Regards,
Bernd Spickers