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

List:       kde-community
Subject:    Re: using gitlab ultimate
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-08-03 11:53:26
Message-ID: CA+XidOEC9D_y0F=w=4r=kBsFEizF6JLFqnqh+Np9ED_c6qPLAw () mail ! gmail ! com
[Download RAW message or body]

On Thu, Aug 3, 2023 at 1:31 AM Harald Sitter <sitter@kde.org> wrote:

> Ahoy!
>
> How about we start using the gitlab ultimate rather than the free version?
>
> It'd give us access to some handy dandy features like
>
> - CI dashboard
> - multiple MR assignees
> - better issue boards
> - epics & roadmaps
> - dependency scanning support (for our supporting projects written in
> ruby, go, python etc)
>

With regards to the above:

The CI dashboards offered by Gitlab EE (Ultimate) would still be
insufficient for our needs from what I can tell in the documentation. We
need to be able to see down to the job level to separate based on platform
/ checks failing, which isn't supported functionality. For this we will
need to develop something different and custom, and unlike the previous
iterations won't be able to make use ot Grafana (as Gitlab CI statuses just
isn't something that fits well within the Prometheus/Grafana model)

With respect to dependency scanning, the core functionality is still
available and the raw reports are published to Gitlab, what is missing is
the visualisation (much like test reports on commits).

For issue boards, we've yet to fully do that migration - but when we do
switch off Phabricator and bring it's content into Gitlab - we can
definitely look at asking for bits and pieces of functionality to be moved
over as Eike mentioned.
We were already successful in getting multiple boards moved over (for the
project level).

I have plans surrounding MR assignees, watch this space....

Much like the rest of the people who have commented here, I agree with the
philosophy of continuing to only use Open Source Software to develop Open
Source Software.


> and that's just off the top of my head!
>
> What do you reckon?
>
> HS
>

Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Thu, Aug 3, 2023 at 1:31 AM Harald Sitter &lt;<a \
href="mailto:sitter@kde.org">sitter@kde.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ahoy!<br> <br>
How about we start using the gitlab ultimate rather than the free version?<br>
<br>
It&#39;d give us access to some handy dandy features like<br>
<br>
- CI dashboard<br>
- multiple MR assignees<br>
- better issue boards<br>
- epics &amp; roadmaps<br>
- dependency scanning support (for our supporting projects written in<br>
ruby, go, python etc)<br></blockquote><div><br></div><div>With regards to the \
above:</div><div><br></div><div>The CI dashboards offered by Gitlab EE (Ultimate) \
would still be insufficient for our needs from what I can tell in the documentation. \
We need to be able to see down to the job level to separate based on platform / \
checks failing, which isn&#39;t supported functionality. For this we will need to \
develop something different and custom, and unlike the previous iterations won&#39;t \
be able to make use ot Grafana (as Gitlab CI statuses just isn&#39;t something that \
fits well within the Prometheus/Grafana model)</div><div><br></div><div>With respect \
to dependency scanning, the core functionality is still available and the raw reports \
are published to Gitlab, what is missing is the visualisation (much like test reports \
on commits).</div><div><br></div><div>For issue boards, we&#39;ve yet to fully do \
that migration - but when we do switch off Phabricator and bring it&#39;s content \
into Gitlab - we can definitely look at asking for bits and pieces of functionality  \
to be moved over as Eike mentioned.</div><div>We were already successful in getting \
multiple boards moved over (for the project level).</div><div><br></div><div>I have \
plans surrounding MR assignees, watch this space....</div><div><br></div><div>Much \
like the rest of the people who have commented here, I agree with the philosophy of \
continuing to only use Open Source Software to develop Open Source \
Software.</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>
and that&#39;s just off the top of my head!<br>
<br>
What do you reckon?<br>
<br>
HS<br></blockquote><div><br></div><div>Thanks,</div><div>Ben  </div></div></div>



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