The warnings plug-in uses the provided Jenkins synchronization http://javadoc.jenkins-ci.org/hudson/tasks/BuildStepMonitor.html#BUILD. I.e. it should block another build of the same job until that result is available. Seems that this is implemented in a different way.

How do you trigger job B in a build step of job A, are you using a plug-in? (Or do you use the post build action "Build other projects"?)

Hi Ulli,
I use the "Trigger/Call builds on other projects" step at job A in the build section and set the option "Block until the triggered projects finish their builds".

Didn't tried it as "Post-build action" yet.
To be honest, first time I found this problem by using the "Build-Flow Build" (Build-Flow-plugin) and calling a subjob in the DSL program code.

I don't see this build step in my setup. Is it coming from another plug-in, e.g. the build-flow plug-in? Maybe this trigger does not implement the correct behavior?

Looks like this step is introduced by "Parameterized Trigger Plugin".

I see. Seems that the maintainer of the Parameterized Trigger plug-in is not active anymore. It is hard to see, which plug-in is doing things wrong.

Would it be possible to reuse the workaround as post build step?

Hi Ulli.

I did some more investigations and found some problems with maven java classes in the logs.
After enabling the plugin "maven-plugin" everything works as expected with "Warnings-plugin".
The end of subjobs with this plugin included is detected properly and do not block anymore.

Regards, Bernd

I have the same issue but I am unable to enable the Maven Integration plugin which I presume is what you mean.
The pop-up message suggest that the Javadoc Plugin plugin in disabled, which I can also confirm but I don't have an option to enable it as it is greyed out.
I am running 1.655 jenkins with quite a lot of other plugins (inc those mentioned in this bug report).
I'd like to get the warning pluging working so any suggestions would be much appreciated.

Hi Mulijan,
I guess last time I should be more precise in the plugin nomination and to be honest I am not sure which "maven-plugin" was meant.
So I checked our configuration and found the same "Maven integration Plugin" you mentioned. We are running Jenkins 1.656 and Maven Integration plugin 2.12.1 and other remaining plugins as well at current versions.

Thanks for the update bspickers. I seem to have fixed the issue by manually deleting the javadoc.jpi.disabled and maven-plugin.jpi.disabled files in the jenkins Plugin folder.