On 31 August 2017 at 12:25, Martin Perina <[email protected]> wrote: > > > On Thu, Aug 31, 2017 at 11:22 AM, Barak Korren <[email protected]> wrote: >> >> On 31 August 2017 at 12:16, Martin Perina <[email protected]> wrote: >> > >> > On Thu, Aug 31, 2017 at 11:09 AM, Barak Korren <[email protected]> >> > wrote: >> >> >> >> As a temporary measure, we can disable the automated deployment from >> >> jobs that run on PR messages. But this means that we will need to do >> >> the deployment manually when needed. >> > >> > Seems like good idea, as we really need to add to tested queue only >> > merged >> > PRs. How exactly will we be able to perform that manually? >> >> For the 1st few times, please ask me to do it. After that I'll either >> have automation in place or be certain enough about how to do it to be >> able to explain it to someone else. >> >> Actually I think that if we go for this, I might be able to replace >> your existing jobs with the new code (It supports 99% of what the >> existing code can do with PRs), and at least be rid of the nagging bot >> messages for new PR submitters. > > > OK, so please let's try this approach.
Ok. This patch makes the existing jobs not deploy: https://gerrit.ovirt.org/#/c/81268/ I don't want to risk making the existing jobs not work for the weekend so I will not replace them with new code today. Instead I will set them to run side by side with existing jobs. I'm only seeing jobs for ovirt-ansible. Are we supposed to also have jobs for 'ovirt-ansible-modules'? -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
