[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Rollout of Gitlab CI
From: Johnny Jazeix <jazeix () gmail ! com>
Date: 2021-09-29 18:01:35
Message-ID: CAEtcAPEg8cBmhAYbQVRy-4NwYj2jOo2sgoHZ=BwRKmAu+B23oA () mail ! gmail ! com
[Download RAW message or body]
Le mer. 29 sept. 2021 =C3=A0 19:37, Ben Cooksley <bcooksley@kde.org> a =C3=
=A9crit :
> On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix <jazeix@gmail.com> wrote:
>
>>
>>
>> Le mer. 29 sept. 2021 =C3=A0 11:27, Ben Cooksley <bcooksley@kde.org> a =
=C3=A9crit :
>>
>>> Hi all,
>>>
>>> As those of you who watch and work on Frameworks repositories will be
>>> aware, we've just rolled out the first set of native Gitlab CI builds.
>>>
>>> These builds are at this time Linux only, but do include support for
>>> both regular branch builds as well as for Merge Requests. It is anticip=
ated
>>> that Windows, FreeBSD and Android builds will follow in the near future=
-
>>> there are a few extra things we need to get completed first before they=
can
>>> be rolled out. As part of carrying out the build the scripts will also
>>> gather Code Coverage and Code Quality information using gcovr and cppch=
eck
>>> respectively, and this will be made available to you within the Gitlab
>>> interface.
>>>
>>> With regards to availability to projects outside Frameworks, projects
>>> that depend only on Frameworks (and no other KDE project) may enable CI=
for
>>> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml fi=
les
>>> to their repositories. I anticipate that once the necessary changes hav=
e
>>> been made to the "seed" jobs used to provision the initial artifacts it
>>> should be possible for all projects to rollout support (although i'd li=
ke
>>> to add ccache support to the system to ensure larger project builds
>>> complete promptly first).
>>>
>>> If anyone would like to help out with getting the seed jobs ready pleas=
e
>>> let me know as this is definitely something that the community can assi=
st
>>> with (and will also help with easing the rollout of Windows, FreeBSD an=
d
>>> Android builds).
>>>
>>> For those projects that do go ahead with enabling Gitlab CI support
>>> please ensure you add the necessary .kde-ci.yml file beforehand, specif=
ying
>>> in it the necessary Dependencies, as well as the necessary Options your
>>> project needs to customise for their build. A list of all the possible
>>> values in a .kde-ci.yml file can be found at
>>> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-templ=
ate.yml#L10
>>>
>>> For those projects that are not yet able to enable the system, it is
>>> strongly encouraged that you go ahead and get the .kde-ci.yml files rea=
dy
>>> in your repository now - especially if other projects depend on your
>>> project. This will allow the rollout of the CI system to those projects=
to
>>> proceed much more smoothly (otherwise we will need to get them added to
>>> those projects which have other projects depending on them).
>>>
>>> Please note that this new infrastructure replaces all existing Gitlab C=
I
>>> jobs we provided in the initial testing phase, and those should be remo=
ved
>>> (much like how I did for Frameworks) when switching to the new setup.
>>>
>>> Thanks,
>>> Ben
>>>
>>
>> Hi,
>>
>> is there a template for the .gitlab-ci.yml or should we use the same as
>> https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521=
d245e3a1ea50109b86a2b716966938e
>> for example?
>>
>
> You can use the same as that file.
>
> We're not providing a .gitlab-ci.yml template as there will be Windows,
> FreeBSD and Android builds as well (and potentially in the future macOS a=
s
> well) which are options that won't necessarily apply to all projects.
>
>
>> Cheers,
>>
>> Johnny
>>
>
> Cheers,
> Ben
>
Ok, super. It works fine for GCompris:
https://invent.kde.org/education/gcompris/-/tree/master
Thanks for providing this!
Johnny
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">Le mer. 29 sept. 2021 Ã 19:37, Ben Cooksley <<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>> a écrit \
:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 30, 2021 at 3:41 AM \
Johnny Jazeix <<a href="mailto:jazeix@gmail.com" \
target="_blank">jazeix@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 29 sept. 2021 Ã \
11:27, Ben Cooksley <<a href="mailto:bcooksley@kde.org" \
target="_blank">bcooksley@kde.org</a>> a écrit :<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi \
all,</div><div><br></div><div>As those of you who watch and work on Frameworks \
repositories will be aware, we've just rolled out the first set of native Gitlab \
CI builds.</div><div><br></div><div>These builds are at this time Linux only, but do \
include support for both regular branch builds as well as for Merge Requests. It is \
anticipated that Windows, FreeBSD and Android builds will follow in the near future - \
there are a few extra things we need to get completed first before they can be rolled \
out. As part of carrying out the build the scripts will also gather Code Coverage and \
Code Quality information using gcovr and cppcheck respectively, and this will be made \
available to you within the Gitlab interface.</div><div><br></div><div>With regards \
to availability to projects outside Frameworks, projects that depend only on \
Frameworks (and no other KDE project) may enable CI for their project by adding the \
necessary .kde-ci.yml and .gitlab-ci.yml files to their repositories. I anticipate \
that once the necessary changes have been made to the "seed" jobs used to \
provision the initial artifacts it should be possible for all projects to rollout \
support (although i'd like to add ccache support to the system to ensure larger \
project builds complete promptly first).</div><div><br></div><div>If anyone would \
like to help out with getting the seed jobs ready please let me know as this is \
definitely something that the community can assist with (and will also help with \
easing the rollout of Windows, FreeBSD and Android \
builds).<br></div><div><br></div><div>For those projects that do go ahead with \
enabling Gitlab CI support please ensure you add the necessary .kde-ci.yml file \
beforehand, specifying in it the necessary Dependencies, as well as the necessary \
Options your project needs to customise for their build. A list of all the possible \
values in a .kde-ci.yml file can be found at <a \
href="https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10" \
target="_blank">https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10</a></div><div><br></div><div>For \
those projects that are not yet able to enable the system, it is strongly encouraged \
that you go ahead and get the .kde-ci.yml files ready in your repository now - \
especially if other projects depend on your project. This will allow the rollout of \
the CI system to those projects to proceed much more smoothly (otherwise we will need \
to get them added to those projects which have other projects depending on \
them).<br></div><div><br></div><div>Please note that this new infrastructure replaces \
all existing Gitlab CI jobs we provided in the initial testing phase, and those \
should be removed (much like how I did for Frameworks) when switching to the new
setup.</div><div><br></div><div>Thanks,</div><div>Ben<br></div></div></blockquote><div><br></div><div>
<div>Hi,</div><div><br></div><div>is there a template for the
.gitlab-ci.yml
or should we use the same as
<a href="https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e" \
target="_blank">https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e</a>
for example?</div></div></div></div></blockquote><div><br></div><div>You can use \
the same as that file.</div><div><br></div><div>We're not providing a \
.gitlab-ci.yml template as there will be Windows, FreeBSD and Android builds as well \
(and potentially in the future macOS as well) which are options that won't \
necessarily apply to all projects.</div><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div><div><br></div><div>Cheers,</div><div><br></div><div>Johnny</ \
div></div></div></div></blockquote><div><br></div><div>Cheers,</div><div>Ben<br></div></div></div></blockquote><div><br></div><div>Ok, \
super. It works fine for GCompris: <a \
href="https://invent.kde.org/education/gcompris/-/tree/master">https://invent.kde.org/education/gcompris/-/tree/master</a></div><div><br></div><div>Thanks \
for providing this!</div><div><br></div><div>Johnny<br></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic