-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.11, Multijob 1.21, SWARM/2015.4/1331216
When using the multijob plugin (https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin), builds triggered as part of a multijob phase report their statuses back to the triggering Swarm review, in addition to the parent multijob itself. This results in duplicate notifications for a single change.
It's unclear to me how the P4 plugin determines how and why to report build status back to Swarm, but my best guess is that it looks for the existence of build parameters such as review, pass, and fail. By default, multijobs pass all build parameters through to child jobs, so this is likely the culprit. If it is the build paramters that are responsible, it can be worked around by not passing build parameters through to children, but this makes it more difficult to ensure changelist synchronization between the parent multijob and the child jobs it triggers.