[openstack-dev] [tripleo] CI is down stop workflowing
Hi, We have the following bugs with fixes that need to land to unblock check/gate jobs: https://bugs.launchpad.net/tripleo/+bug/1777451 https://bugs.launchpad.net/tripleo/+bug/1777616 You can check them out at #tripleo ooolpbot. Please stop workflowing temporally until they get merged. BR. -- Quique Llorente Openstack TripleO CI __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] Proposing Enrique Llorente Pastora as a core reviewer for TripleO
Thanks guys! On Fri, Nov 16, 2018 at 8:26 AM Martin André wrote: > On Thu, Nov 15, 2018 at 5:00 PM Wesley Hayutin > wrote: > > > > > > > > On Thu, Nov 15, 2018 at 8:52 AM Sagi Shnaidman > wrote: > >> > >> Hi, > >> I'd like to propose Quique (@quiquell) as a core reviewer for TripleO. > Quique is actively involved in improvements and development of TripleO and > TripleO CI. He also helps in other projects including but not limited to > Infrastructure. > >> He shows a very good understanding how TripleO and CI works and I'd > like suggest him as core reviewer of TripleO in CI related code. > >> > >> Please vote! > >> My +1 is here :) > > > > > > +1 for tripleo-ci core, I don't think we're proposing tripleo core atm. > > Thanks for proposing and sending this Sagi! > > +1 > > Martin > > >> > >> > >> Thanks > >> -- > >> Best regards > >> Sagi Shnaidman > >> > __ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Quique Llorente Openstack TripleO CI __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo][ci] Having more that one queue for gate pipeline at tripleo
Hello there, After suffering a lot from zuul's tripleo gate piepeline queue reseting after failures on patches I have ask myself what would happend if we have more than one queue for gating tripleo. After a quick read here https://zuul-ci.org/docs/zuul/user/gating.html, I have found the following: "If changes with cross-project dependencies do not share a change queue then Zuul is unable to enqueue them together, and the first will be required to merge before the second is enqueued." So it make sense to share zuul queue, but maybe only one queue for all tripleo projects is too much, for example sharing queue between tripleo-ui and tripleo-quickstart, maybe we need for example to queues for product stuff and one for CI, so product does not get resetted if CI fails in a patch. What do you think ? -- Quique Llorente Openstack TripleO CI __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][ci] Having more that one queue for gate pipeline at tripleo
So for example, I don't see why changes at tripleo-quickstart can be reset if tripleo-ui fails, this is the kind of thing that maybe can be optimize. On Thu, Oct 11, 2018 at 1:17 PM Emilien Macchi wrote: > > > On Thu, Oct 11, 2018 at 10:01 AM Felix Enrique Llorente Pastora < > ellor...@redhat.com> wrote: > >> Hello there, >> >>After suffering a lot from zuul's tripleo gate piepeline queue >> reseting after failures on patches I have ask myself what would happend if >> we have more than one queue for gating tripleo. >> >>After a quick read here https://zuul-ci.org/docs/zuul/user/gating.html, >> I have found the following: >> >> "If changes with cross-project dependencies do not share a change queue >> then Zuul is unable to enqueue them together, and the first will be >> required to merge before the second is enqueued." >> >>So it make sense to share zuul queue, but maybe only one queue for all >> tripleo projects is too much, for example sharing queue between tripleo-ui >> and tripleo-quickstart, maybe we need for example to queues for product >> stuff and one for CI, so product does not get resetted if CI fails in a >> patch. >> >>What do you think ? >> > > Probably a wrong example, as TripleO UI gate is using CI jobs running > tripleo-quickstart scenarios. > We could create more queues for projects which are really independent from > each other but we need to be very careful about it. > -- > Emilien Macchi > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Quique Llorente Openstack TripleO CI __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
