[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Rollout of Gitlab CI
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2021-10-03 7:38:42
Message-ID: CA+XidOFDNb_G0Jmu_g0c0VC+fm0QWsj67N5bP-8dGMpUw2AD7g () mail ! gmail ! com
[Download RAW message or body]

On Fri, Oct 1, 2021 at 10:40 AM David Hurka <david.hurka@mailbox.org> wrote:

> On Thursday, September 30, 2021 10:12:35 PM CEST Albert Astals Cid wrote:
> > Does this means we can no longer have interesting CI like
> >   "install this special distro that has openssl3 so that the QCA code
> > doesn't regress" or
> >   "install this old Ubuntu since we still want to code to build in an
> older
> > Qt version" ?
>
> Yeah, the "GitLab CI" that comes with GitLab will probably stay, and just
> the
> CI templates in the sysadmin repositories will be removed?
>

> .gitlab-ci.yml allows to define quite flexible scenarios, but most KDE
> repositories which I have seen just include a few templates from the
> sysadmin
> repositories, so I assume you are talking about the latter. :)
>

That is correct.

Given that it is not an uncommon scenario, we may consider adding specific
CI support for an LTS distribution (potentially along with it's
corresponding Frameworks) depending on the interest.
The new system makes it substantially easier to add more platforms compared
with our Jenkins environment (which was a bit of a nightmare tbh).


> > Cheers,
> >   Albert
> >
> > > Thanks,
> > > Ben
>
> Cheers, David
>

Cheers,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct \
1, 2021 at 10:40 AM David Hurka &lt;<a \
href="mailto:david.hurka@mailbox.org">david.hurka@mailbox.org</a>&gt; \
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">On Thursday, September \
30, 2021 10:12:35 PM CEST Albert Astals Cid wrote:<br> &gt; Does this means we can no \
longer have interesting CI like<br> &gt;     &quot;install this special distro that \
has openssl3 so that the QCA code<br> &gt; doesn&#39;t regress&quot; or<br>
&gt;     &quot;install this old Ubuntu since we still want to code to build in an \
older<br> &gt; Qt version&quot; ?<br>
<br>
Yeah, the "GitLab CI" that comes with GitLab will probably stay, and just the <br>
CI templates in the sysadmin repositories will be removed? \
<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
.gitlab-ci.yml allows to define quite flexible scenarios, but most KDE <br>
repositories which I have seen just include a few templates from the sysadmin <br>
repositories, so I assume you are talking about the latter. \
:)<br></blockquote><div><br></div><div>That is \
correct.</div><div><br></div><div>Given that it is not an uncommon scenario, we may \
consider adding specific CI support for an LTS distribution (potentially along with \
it&#39;s corresponding Frameworks) depending on the interest.</div><div>The new \
system makes it substantially easier to add more platforms compared with our Jenkins \
environment (which was a bit of a nightmare tbh).</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"> <br>
&gt; Cheers,<br>
&gt;     Albert<br>
&gt; <br>
&gt; &gt; Thanks,<br>
&gt; &gt; Ben<br>
<br>
Cheers, David<br></blockquote><div><br></div><div>Cheers,</div><div>Ben<br></div></div></div>




[prev in list] [next in list] [prev in thread] [next in thread]