+1, this will be the best suggestion. we can try adding a manual trigger for drafts if needed, still need to check if possible. e. On Wed, Dec 9, 2015 at 9:38 AM, Eli Mesika <emesika@redhat.com> wrote:
----- Original Message -----
From: "Barak Korren" <bkorren@redhat.com> To: "Amit Aviram" <aaviram@redhat.com> Cc: "infra" <infra@ovirt.org> Sent: Tuesday, December 8, 2015 5:16:30 PM Subject: Re: Actively triggering of CI jobs
I was thinking, maybe it would be better if we will explicitly require to run the CI jobs when we push patches.. then only when the developer will need the job's feedback it will be activated. no redundant jobs will run, and we will wait much less for the jobs to finish when we will actually need them.
Why not simply submit your patches as a Draft until the point you want CI to run on them, then you can simply publish them ... This is the way I am using and it's simple ...
It seems to me that it will me too easy to forget to run the CI this way.
There is another way though - To make the jobs do a lot less work. Most anything has to do what what actually happens in CI resides in the project`s automation directory now days (see [1]). If you want to make CI smarter so it will not do things it shouldn't be doing, all you need to do is customize the automation scripts to be smarter and run only the needed tests for the files that were changed by the patch.
[1]: http://www.ovirt.org/CI/Build_and_test_standards
-- Barak Korren bkorren@redhat.com RHEV-CI Team _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)