On Tue, Aug 6, 2019 at 5:07 PM Nir Soffer <[email protected]> wrote:
> On Tue, Aug 6, 2019 at 5:01 PM Amit Bawer <[email protected]> wrote: > >> >> >> On Tue, Aug 6, 2019 at 4:58 PM Nir Soffer <[email protected]> wrote: >> >>> On Tue, Aug 6, 2019 at 11:27 AM Amit Bawer <[email protected]> wrote: >>> >>>> I have seen some improvement: when I re-trigger the CI per patch I am >>>> able to pass or get the actual test errors if any (if not on first try, >>>> then on second one). >>>> Probably not a very useful information, but I have noticed that when I >>>> push 30+ patches at the same >>>> >>> >>> Do not do that, jenkins cannot handle 30 concurrent builds, and is it >>> also bad for reviewers, >>> getting several mails about every patch in your chain, for every rebase. >>> >> >> Is there is a way to prevent CI from running per gerrit push (without >> working on 30 different branches) ? >> > > I don't know about such way. > A legit option could be adding the Skip CI plugin to jenkins plugins [1]; with that devs can add "[skip ci]" to their commit messages to prevent jenkins from automatically launching CI upon push. Another option is to emulate the behaviour in the existing gerrit plugin (guess there is already such one in ovirt's jenkins), for example skipping by a topic regex [2]. [1] https://plugins.jenkins.io/ci-skip [2] https://stackoverflow.com/questions/37807941/how-can-i-get-jenkins-gerrit-trigger-to-ignore-my-ci-users-commits > > I'm using keeping several small active branches. While you wait for > reviews on one topic > you can work on the other branches. > > > >> >>> >>>> time the AWS connection issue arises constantly. >>>> >>>> On Sun, Aug 4, 2019 at 4:49 PM Eyal Edri <[email protected]> wrote: >>>> >>>>> This was reported already and AFAIK its a network issue between AWS >>>>> and PHX which is still being investigated. >>>>> Evgheni, any insights or update on the issue? should we involve >>>>> debugging from amazon side? >>>>> >>>>> On Sun, Aug 4, 2019 at 4:46 PM Amit Bawer <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> CI seems to fail constantly for unavailable remote gerrit repository. >>>>>> Example can be seen here: >>>>>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/9415/console >>>>>> _______________________________________________ >>>>>> Devel mailing list -- [email protected] >>>>>> To unsubscribe send an email to [email protected] >>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>> oVirt Code of Conduct: >>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>> List Archives: >>>>>> https://lists.ovirt.org/archives/list/[email protected]/message/AHPHUZAABAQNWEMD2JQ6WARHJRDTYCPI/ >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Eyal edri >>>>> >>>>> He / Him / His >>>>> >>>>> >>>>> MANAGER >>>>> >>>>> CONTINUOUS PRODUCTIZATION >>>>> >>>>> SYSTEM ENGINEERING >>>>> >>>>> Red Hat <https://www.redhat.com/> >>>>> <https://red.ht/sig> >>>>> phone: +972-9-7692018 >>>>> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) >>>>> >>>> _______________________________________________ >>>> Devel mailing list -- [email protected] >>>> To unsubscribe send an email to [email protected] >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/[email protected]/message/W6DUMIUSN5DPUVGUFUNHF2ZALB5I4JPZ/ >>>> >>>
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/FIQNCVGEKADDZ3XC65QYSI5TCCTPEIKS/
