FYI, in the case of openflowplugin project this comes for free, you can start using "test-openflowplugin" right away. System test triggered by this keyword is in this file:
https://git.opendaylight.org/gerrit/#/c/40989/1/jjb/openflowplugin/openflowplugin-patch-test.yaml <https://git.opendaylight.org/gerrit/#/c/40989/1/jjb/openflowplugin/openflowplugin-patch-test.yaml> BR/Luis > Begin forwarded message: > > From: Luis Gomez <[email protected]> > Subject: Project Patch Test job > Date: June 29, 2016 at 5:38:00 PM PDT > To: "release ([email protected])" > <[email protected]> > Cc: [email protected] > > Hi all, > > For those familiar with "test-integration" keyword, we have a new jjb > template that allows projects to define their own system test to run on a > project patch. Same as "test-integration" this is useful for committers to > verify incoming patches but without the burden of triggering all the system > test available in ODL. The new keyword once the job is set (see instructions > below) is "test-{project}". > > https://wiki.opendaylight.org/view/Integration/Test/Step_by_Step_Guide_To_Creating_System_Tests#Optional:_Add_Patch_Test_Job_to_verify_project_gerrits > > <https://wiki.opendaylight.org/view/Integration/Test/Step_by_Step_Guide_To_Creating_System_Tests#Optional:_Add_Patch_Test_Job_to_verify_project_gerrits> > > We really encourage projects to use this new job over the existing > "test-integration", mainly because of the resources saving. > > BR/Luis >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
