Hi, This is in our plans since last year. The idea is to come up with a common format to use in commit message which gets processed by the verify job, running the impacted scenario.
Please see the first step in below section. https://wiki.opnfv.org/display/INF/CI+Evolution#CIEvolution-HowtheThingsFitTogether We are currently working on aligning job structures (verify and daily) and scope of the patchset verification for all the installers since the current situation is not good, some do things properly some does nothing. Here is who does what as part of patchset verification. - apex: unit test, build, virtual deploy, functest smoke test - compass: lint, virtual deploy, functest smoke test - daisy: build, virtual deploy - fuel: build - joid: nothing Apart from not reaching to this step to come up with a proposal for commit message, this depends on scenario consolidation/naming activity as well. We can hopefully start working with this after Danube. /Fatih From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Yujun Zhang <zhangyujun+...@gmail.com> Date: Tuesday, 24 January 2017 at 08:41 To: Chigang <chig...@huawei.com>, "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion I think it is technically feasible. We added an experimental trigger for doctor project not long ago[1]. The trigger is similar to your requirement. [1]: https://gerrit.opnfv.org/gerrit/#/c/26839/4/jjb/global/releng-macros.yml On Tue, Jan 24, 2017 at 12:31 PM Chigang (Justin) <chig...@huawei.com<mailto:chig...@huawei.com>> wrote: Hi, The Command "recheck" is used to run default patch verification again in Gerrit. But there are so many scenarios to be vericated, I think default patch verification is not enough. Is it possible to add a "scenarios" parameters to improve additional verification before patch merged in master? such as : "recheck odl" will trigged to odl related scenarios. Thanks Justin _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
