From: Adam Jackson <ajax@redhat.com>
To: "Rob Clark" <robdclark@gmail.com>, "Michel Dänzer" <michel@daenzer.net>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"X.Org development" <xorg-devel@lists.x.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
wayland <wayland-devel@lists.freedesktop.org>,
"X.Org Foundation Board" <board@foundation.x.org>,
Xorg Members List <members@x.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Mesa Dev <mesa-dev@lists.freedesktop.org>,
Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>
Subject: Re: [Mesa-dev] [Intel-gfx] gitlab.fd.o financial situation and impact on services
Date: Mon, 06 Apr 2020 11:42:54 -0400 [thread overview]
Message-ID: <f4d856925111b77012cabb255d6a880ae5637b41.camel@redhat.com> (raw)
In-Reply-To: <CAF6AEGuNTtHfNm_nRhPFX5wPRmKkjnFEKqTdTSBDjpLkaiN8Fw@mail.gmail.com>
On Sat, 2020-04-04 at 08:11 -0700, Rob Clark wrote:
> On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer <michel@daenzer.net> wrote:
> > On 2020-03-01 6:46 a.m., Marek Olšák wrote:
> > > For Mesa, we could run CI only when Marge pushes, so that it's a strictly
> > > pre-merge CI.
> >
> > Thanks for the suggestion! I implemented something like this for Mesa:
> >
> > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432
>
> I wouldn't mind manually triggering pipelines, but unless there is
> some trick I'm not realizing, it is super cumbersome. Ie. you have to
> click first the container jobs.. then wait.. then the build jobs..
> then wait some more.. and then finally the actual runners. That would
> be a real step back in terms of usefulness of CI.. one might call it a
> regression :-(
I think that's mostly a complaint about the conditionals we've written
so far, tbh. As I commented on the bug, when I clicked the container
job (which the rules happen to have evaluated to being "manual"), every
job (recursively) downstream of it got enqueued, which isn't what
you're describing. So I think if you can describe the UX you'd like we
can write rules to make that reality.
But I don't really know which jobs are most expensive in terms of
bandwidth, or storage, or CPUs, and even if I knew those I don't know
how to map those to currency. So I'm not sure if the UI we'd like would
minimize the cost the way we'd like.
- ajax
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-06 15:43 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 21:27 gitlab.fd.o financial situation and impact on services Daniel Vetter
2020-02-27 23:45 ` Matt Turner
2020-02-28 7:59 ` Daniel Stone
2020-02-28 10:09 ` Jan Engelhardt
2020-02-28 11:11 ` Daniel Stone
2020-02-28 21:20 ` Matt Turner
2020-02-28 0:21 ` Luc Verhaegen
2020-02-28 0:33 ` Carsten Haitzler
2020-02-28 1:00 ` [Mesa-dev] " Tom Stellard
2020-02-28 1:08 ` Tom Stellard
2020-02-28 3:37 ` [Intel-gfx] " Dave Airlie
2020-02-28 7:44 ` Daniel Vetter
2020-02-28 8:17 ` Daniel Stone
2020-02-28 8:48 ` Dave Airlie
2020-02-28 9:26 ` Daniel Stone
2020-02-28 19:34 ` [Mesa-dev] " Eric Anholt
2020-02-28 20:30 ` Dave Airlie
2020-02-28 21:22 ` Daniel Vetter
2020-02-28 21:37 ` Nuritzi Sanchez
2020-04-04 13:55 ` Andreas Bergmeier
2020-04-05 14:07 ` Nicolas Dufresne
2020-02-28 9:28 ` Erik Faye-Lund
2020-02-28 9:40 ` Lionel Landwerlin
2020-02-28 10:06 ` Erik Faye-Lund
2020-02-28 10:43 ` Daniel Stone
2020-02-28 11:02 ` Erik Faye-Lund
2020-02-28 11:46 ` Michel Dänzer
2020-02-28 13:08 ` Lionel Landwerlin
2020-02-29 18:14 ` Timur Kristóf
2020-02-29 19:46 ` Nicolas Dufresne
2020-02-29 20:28 ` Timur Kristóf
2020-02-29 21:54 ` Jason Ekstrand
2020-02-29 22:20 ` Nicolas Dufresne
2020-03-01 5:46 ` Marek Olšák
2020-04-03 14:12 ` Michel Dänzer
2020-04-04 15:11 ` Rob Clark
2020-04-04 17:47 ` Nicolas Dufresne
2020-04-04 18:16 ` Rob Clark
2020-04-04 18:41 ` Rob Clark
2020-04-04 18:47 ` Rob Clark
2020-04-04 23:39 ` Peter Hutterer
2020-04-04 23:32 ` Peter Hutterer
2020-04-06 15:42 ` Adam Jackson [this message]
2020-04-06 16:34 ` Rob Clark
2020-04-06 17:04 ` Michel Dänzer
2020-04-06 18:00 ` Rob Clark
2020-03-01 14:14 ` [Mesa-dev] [Intel-gfx] " Michel Dänzer
2020-03-01 14:27 ` Nicolas Dufresne
2020-03-01 19:51 ` Jacob Lifshay
2020-03-01 20:18 ` [Intel-gfx] [Mesa-dev] " Jason Ekstrand
2020-03-01 20:30 ` Bridgman, John
2020-03-01 20:49 ` Nicolas Dufresne
2020-03-02 4:53 ` Jason Ekstrand
2020-02-28 9:47 ` [Mesa-dev] [Intel-gfx] " Daniel Vetter
2020-02-28 10:10 ` Erik Faye-Lund
2020-02-28 10:27 ` Lucas Stach
2020-02-28 11:43 ` Michel Dänzer
2020-02-28 17:00 ` [Intel-gfx] [Mesa-dev] " Rob Clark
2020-02-29 15:58 ` Jason Ekstrand
2020-02-28 18:03 ` [Intel-gfx] " Kristian Høgsberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f4d856925111b77012cabb255d6a880ae5637b41.camel@redhat.com \
--to=ajax@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=board@foundation.x.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=members@x.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=michel@daenzer.net \
--cc=robdclark@gmail.com \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xorg-devel@lists.x.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).