[igt-dev] [PATCH i-g-t v2] Add GitLab's CI/CD configuration

Daniel Vetter daniel at ffwll.ch
Mon Oct 22 14:18:56 UTC 2018


On Mon, Oct 22, 2018 at 4:15 PM Arkadiusz Hiler
<arkadiusz.hiler at intel.com> wrote:
>
> On Mon, Oct 22, 2018 at 03:09:04PM +0300, Arkadiusz Hiler wrote:
> > The CI/CD pipeline is configured the following way:
> >  1. Build docker images and add them to repo's registry (manual step for
> >     now, automation needs GitLab to be updated).
> >  2. Build igt with meson on Debian and Fedora.
> >  3. Run `ninja tests` on Fedora.
> >  4. Build and publish docs as an artifact, for GitLab Pages.
> >
> > v2: Typos and fully-featured meson build.
> >
> > Cc: Petri Latvala <petri.latvala at intel.com>
> > Cc: Daniel Vetter <daniel at ffwll.ch>
> > Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
>
> Both images are already in our registry.
>
> Here you can see the pipline running (on a testing branch):
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/pipelines/6292

I think the "proper" gitlab way of doing this is not through a
temporary branch, but through a merge request. Or a personal fork.
Gives you the exact same amount of gitlab-ci testing as a branch. Just
an aside, figure we'll start with the process bikeshedding right away
:-)
-Daniel

> There's no pages stage, as it is limited to master branch only.
> I've got it tested in my private repo:
> https://gitlab.freedesktop.org/ivyl/igt/pipelines/5159
>
> --
> Cheers,
> Arek



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch


More information about the igt-dev mailing list