[Mesa-ci-intel] New CI branch for Mesa 18.3.x series

Emil Velikov emil.l.velikov at gmail.com
Thu Nov 8 16:09:07 UTC 2018


On Wed, 7 Nov 2018 at 17:40, Clayton Craft <clayton.a.craft at intel.com> wrote:
>
> Quoting Emil Velikov (2018-11-07 09:35:08)
> > On Mon, 5 Nov 2018 at 09:32, Juan A. Suarez Romero <jasuarez at igalia.com> wrote:
> >
> > > I'd like to say that for 18.2, we were using Mesa repository, not our own
> > > repository. I think this was agreed in a thread some time ago. And I think this
> > > should be kept for 18.3, so everything happens in the mesa repository.
> > >
> > Now that you mention, I details are coming to me.
> > Looking at the docs - we forgot to follow-up with documentation updates.
> > Sent some earlier - comments are appreciated.
> >
> > > As I said, it would be great if we continue using a similar approach for 18.3
> > > branches.
> > >
> > Ack.
> >
> > > Basically, we take a look at https://mesa-ci.01.org/, where the results for
> > > staging/18.2 and staging/18.2-ci are pushed. In our side we do nothing, only
> > > push commits to those branches.
> > >
> > > If we see that no results were pushed, then we ask Clayton/Mark, as probably
> > > something was broken in the CI and manually work is required.
> > >
> > Smashing thanks. Can you write a patch that adds this information to
> > the Mesa docs?
> >
> > Clayton/Mark,
> > Please swap my silly wip/18.3 with the staging/18.3 branch from the
> > upstream repo.
>
> Done. After about 10 minutes can you push something to the branch to test that
> CI triggers properly?
>
Cannot see anything at mesa-ci.01.org. Since I don't want to nag you
guys too often, how long after the push should one expect to see
results?

Thanks
Emil


More information about the Mesa-ci-intel mailing list