Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion
Hi, Fatih I was just wondering if it would be possible to trigger experimental jobs from commit message instead of comment. Any example of using commit message as trigger in current jobs? What I want to achieve is to trigger doctor profiling jobs when I include a tag in commit message, e.g. [ci profiling]. Is that possible with current OPNFV CI? On Mon, Jan 30, 2017 at 9:53 PM Fatih Degirmenci < fatih.degirme...@ericsson.com> wrote: > Hi Yujun, > > > > We don't plan to use an additional plugin since the commit message is > injected into job environment (GERRIT_CHANGE_COMMIT_MESSAGE) by the Gerrit > Trigger plugin. [1] That will be processed by the parent multijob, passing > the scenario name into the phase jobs/scripts. > > > > We can extend this and make it possible for triggering (additional) jobs > for other impacted scenarios by comments to patchset - like how you do > similar things for doctor. > > > > [1] > https://build.opnfv.org/ci/view/doctor/job/doctor-verify-master/351/injectedEnvVars/ > > > > /Fatih > > > > *From: *Yujun Zhang <zhangyujun+...@gmail.com> > *Date: *Monday, 30 January 2017 at 13:40 > *To: *Fatih Degirmenci <fatih.degirme...@ericsson.com>, 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 > > > > Hi, Fatih > > It seems your proposal is based on commit message. > > > > Are you referring to Commit Message Trigger Plugin[1]? Is the plugin > already installed on OPNFV CI? > > > > [1]: > https://wiki.jenkins-ci.org/display/JENKINS/Commit+Message+Trigger+Plugin > > > > On Tue, Jan 24, 2017 at 5:15 PM Fatih Degirmenci < > fatih.degirme...@ericsson.com> wrote: > > 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> > 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 > 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
Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion
Hi, Fatih It seems your proposal is based on commit message. Are you referring to Commit Message Trigger Plugin[1]? Is the plugin already installed on OPNFV CI? [1]: https://wiki.jenkins-ci.org/display/JENKINS/Commit+Message+Trigger+Plugin On Tue, Jan 24, 2017 at 5:15 PM Fatih Degirmenci < fatih.degirme...@ericsson.com> wrote: > 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> > 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 > 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
Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion
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
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)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 > 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
[opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion
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 https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss