I really like the idea of cleaning and totally agree with you Luis. The only relevant or monitored comparison is beryllium (he-design) vs. boron (li-design).
(As soon as we don't want to encourage design competition per branch, which I think we don't want.) -al- ________________________________ From: Luis Gomez <[email protected]> Sent: Friday, October 7, 2016 5:01 AM To: Shuva Jyoti Kar Cc: openflowplugin-dev Subject: Re: [openflowplugin-dev] Clean OF test jobs Shuva, we have non-default plugin jobs running for all branches: beryllium (li plugin), boron (li plugin) and carbon (he plugin). Abhijit, we can always recreate a deleted job but there will be no build story for it. In general I think we have too many jobs in ofplugin and I do not feel like creating new ones before we clean the existing, it is already complicated to track what we have today. So please take a look at: https://jenkins.opendaylight.org/releng/view/openflowplugin/ And advice how we can clean this up. BR/Luis On Oct 6, 2016, at 7:13 PM, Shuva Jyoti Kar <[email protected]<mailto:[email protected]>> wrote: Luis as I understand, the non-default plugin jobs would still be running on stable/Be, am I correct ? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Luis Gomez Sent: Friday, October 07, 2016 2:01 AM To: Abhijit Kumbhare Cc: openflowplugin-dev Subject: Re: [openflowplugin-dev] Clean OF test jobs The idea is to remove the jobs so no, we cannot run them again or look at past test results. To be honest I prefer to have few relevant jobs than many jobs we do not look very much: https://jenkins.opendaylight.org/releng/view/openflowplugin/ BR/Luis On Oct 6, 2016, at 1:22 PM, Abhijit Kumbhare <[email protected]<mailto:[email protected]>> wrote: Makes sense but a question: Will we have these tests available if needed even if they are not actually running? On Thu, Oct 6, 2016 at 11:48 AM, Luis Gomez <[email protected]<mailto:[email protected]>> wrote: Hi all, I would like to do some cleaning on existing OF test jobs. The first idea I have is to remove the non-default plugin tests for a given branch: In the past it made sense to compare He plugin vs Li plugin in the same branch so we could track the readiness of the second but after the migration I think it would be enough to just compare Boron vs Beryllium if we want to compare plugins. Also by removing the non-default plugin test we will be cutting the amount of jobs by half. Any concern or comment on this? BR/Luis _______________________________________________ openflowplugin-dev mailing list [email protected]<mailto:[email protected]> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev AndrejLeitner Software Developer Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia R&D centrum / Janka Krála 9 / 974 01 Banská Bystrica / Slovakia / [email protected] reception: +421 2 206 65 114 / www.pantheon.sk [logo]
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
