Sam, Depends on what you mean by trigger. At one point it was the case that if project A depended on project B, project A was expected to have an 'integration' job that got triggered by the project B merge job successfully completing.
It was never blocking (it happened *after* project B's merge job)... but it did give early warning that something bad had happened upstream. Is this the kind of thing you were looking for? Ed On Fri, Mar 24, 2017 at 8:53 AM, Sam Hague <[email protected]> wrote: > Jamo, Thanh, > > was there ever a time when a commit on one project would trigger a > dependent project build? > > We have cases where Netvirt depends on Genius code and a Netvirt UT would > catch any problems. Seems like I remember the infra used to be this way > that a project verify job would also trigger downstream verify jobs - which > would run their UT. > > If that is not in place, is there anything similar we could do? We are > hitting this a lot now. We have CSIT jobs, but those don't run UT so it > doesn't catch these failures. > > Thanks, Sam > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/discuss > >
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
