Original reporter dcendents

I created a Maven multi-branch project and I noticed that many of my branch builds did not record the junit test results, which seemed random. One build would work and the next would not.

I found the problem: when a maven project branch builds "unhindered" then it works normally, however if the "master" project scans for branches and sync the config to the branch projects while a build is in progress, then the junit reporter will not work and it will record 0 junit tests. I find this alarming as the build will pass even if one of my tests fails (should be unstable).

It does not sound safe to systematically push (sync) the configuration to existing branches every time the master project scans the SCM. A perfect solution would be to delay the scan or the sync until all branch projects have finished building. An alternative solution could be to stop syncing the job config every time the project scans for branches and only do it when the master project configuration is modified, which comes down to the user to make sure he is not modifying the configuration while a branch project is building.

Great project by the way, I've been using the lterate plugin for a while but I like that your plugin lets me create "real" jenkins projects with all the available options.

Thanks