On Tue, Sep 7, 2021 at 9:09 PM David Edmundson
wrote:
> Excellent news!! Thanks very much
>
> > Once the scripts have been proven successfully for Frameworks, we will
> look at extending them to projects that depend only on Frameworks and
> repositories
>
> Does this mean we would like Plasma to
Excellent news!! Thanks very much
> Once the scripts have been proven successfully for Frameworks, we will look
> at extending them to projects that depend only on Frameworks and repositories
Does this mean we would like Plasma to wait a while before merging?
Is it worth us creating the kde-cli
On Tue, Sep 7, 2021 at 6:20 AM Johnny Jazeix wrote:
> Hi Ben,
> not sure on which priority it is regarding the KDE Frameworks but I've
> added one on GCompris (
> https://invent.kde.org/education/gcompris/-/commit/67c9839d7970b360b5d6b0ec928b492f9003d07d)
> if it can help on more tests.
>
On Tue, Sep 7, 2021 at 1:04 AM Tom Zander wrote:
> On maandag 6 september 2021 11:48:39 CEST Ben Cooksley wrote:
> > > Pushing everything into required is likely not scalable,
> > > causing projects too wait too long for compile.
> > > Avoiding the optional ones means you lack coverage of
Hi Ben,
not sure on which priority it is regarding the KDE Frameworks but I've
added one on GCompris (
https://invent.kde.org/education/gcompris/-/commit/67c9839d7970b360b5d6b0ec928b492f9003d07d)
if it can help on more tests.
Cheers,
Johnny
Le dim. 5 sept. 2021 à 12:11, Ben Cooksley a écrit :
On 2021-09-06 11:48, Ben Cooksley wrote:
On Mon, Sep 6, 2021 at 9:00 PM Tom Zander wrote:
On zondag 5 september 2021 08:13:09 CEST Ben Cooksley wrote:
In terms of the format of the 'Dependencies' section,
Playing with kde-build script and noticing the fast growing
dependency trees we have
On Mon, Sep 6, 2021 at 9:00 PM Tom Zander wrote:
> On zondag 5 september 2021 08:13:09 CEST Ben Cooksley wrote:
> > In terms of the format of the 'Dependencies' section,
>
> Playing with kde-build script and noticing the fast growing
> dependency trees we have today, I think it may be beneficial
How do we get a visual on exactly which lines are covered by auto testing
and which aren't?
On Mon, Sep 6, 2021 at 12:46 AM Nicolas Fella wrote:
> On 05.09.21 08:13, Ben Cooksley wrote:
> > Hi all,
> >
> > This morning after much work i'm happy to announce that the new
> > generation CI scripts intended for use with Gitlab CI successfully
> > completed their first build (of ECM, and
On Mon, Sep 6, 2021 at 11:03 AM Michael Reeves wrote:
> How do we get a visual on exactly which lines are covered by auto testing
> and which aren't?
>
Please see
https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html
for more details on how this works on Merge
On 05.09.21 08:13, Ben Cooksley wrote:
Hi all,
This morning after much work i'm happy to announce that the new
generation CI scripts intended for use with Gitlab CI successfully
completed their first build (of ECM, and then subsequently of
KCoreAddons).
This begins our first steps towards
On Sun, Sep 5, 2021 at 6:13 PM Ben Cooksley wrote:
> Hi all,
>
Hi all,
> This morning after much work i'm happy to announce that the new generation
> CI scripts intended for use with Gitlab CI successfully completed their
> first build (of ECM, and then subsequently of KCoreAddons).
>
> This
On Sun, 5 Sep 2021 18:13:09 +1200
Ben Cooksley wrote:
> Hi all,
>
> This morning after much work i'm happy to announce that the new generation
> CI scripts intended for use with Gitlab CI successfully completed their
> first build (of ECM, and then subsequently of KCoreAddons).
>
> This begins
Hi all,
This morning after much work i'm happy to announce that the new generation
CI scripts intended for use with Gitlab CI successfully completed their
first build (of ECM, and then subsequently of KCoreAddons).
This begins our first steps towards transferring CI over from Jenkins to
Gitlab.
14 matches
Mail list logo
