Recently, there was a failure which was not detected by the current set of verify jobs: verify, validate-autorelease, distribution-check; even integration-patch-test-* would not detect that.

Here are the e-mails [0], [1]. Basically, a change in binding-parent (Mdsal) had an unintended consequence of affecting behavior of config-parent (Controller), which in turn caused failures in all downstream projects which use config-parent to handle Config SubSystem configfiles.

Additional job is needed (in long term) to catch breakages of this type, but it is not clear to me which compile actions should be performed (and which should be skipped) by such a job. Possibilities range from a small improvement upon validate-autorelease, to basically an autorelease-release build, just with narrowed-down list of projects.

Probably out of scope: An exotic possibility would be to create a script that creates a dummy project from archetypes (of Controller project), so that the dummy project use every parent and code generator well known in ODL. Including karaf-parent, and run a deploy test for such a dummy distribution.

[0] https://lists.opendaylight.org/pipermail/release/2016-August/007764.html
[1] https://lists.opendaylight.org/pipermail/release/2016-August/007823.html