Contributions checks are in no way meant to replace the local tests and are not an assistance for development/authoring the change. They're just an assistance for review (someone else reviewing the change doesn't have to build locally).When I moved us to M7, there were a number of required small tweaks before I had a PR that worked, and that validation happens much more efficiently on local than by submitting it off to Jenkins to build.
Right.And that "blue" PR contained bad changes like the addition of jetty 9.3.6 and a newer Mylyn Wikitext version. Neither of these were caught by the TP build/validation process -- they were caught by downstream install-grinder and p2director install tests.