Another option would be to add {project}-netvirt-check-{stream} to an
existing/new genius patch test job, this way it does not run for every single
patchset but more on-demand.
BR/Luis
> On Apr 6, 2017, at 6:21 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES
> at Cisco) <[email protected]> wrote:
>
> Short answer: netvirt-integration-carbon.
>
> But I guess you want to run the unit tests
> before the code is merged?
>
> We had similar situation with Integration/Distribution
> being the downstream project with sensitive tests.
> We end up creating {project}-distribution-check-{stream}
> to catch breakages before their merge.
>
> I guess you want to create {project}-netvirt-check-{stream}
> and add that to genius verify jobs.
>
> Vratko.
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Sam Hague
> Sent: 24 March, 2017 16:54
> To: <[email protected]> <[email protected]>; Jamo
> Luhrsen <[email protected]>; Thanh Ha <[email protected]>
> Subject: [OpenDaylight Discuss] running verify build for cross project issues
>
> 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
