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.
>
Thanks
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 compile
On maandag 6 september 2021 14:21:00 CEST Christoph Cullmann
(cullmann.io) wrote:
> I would prefer to not have some optional category to be sure
> the CI always builds with the same state of dependencies, too.
A CI build would always build with the latest release (or
whatever the repo owner stat
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 compile
> > and testing failures due to changes in libs.
>
> The
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 to
have two types of compile dependencies in this setup.
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 t
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
On Mon, Sep 6, 2021 at 12:18 AM David Faure wrote:
> On dimanche 5 septembre 2021 12:26:50 CEST Ben Cooksley wrote:
> > On Sun, Sep 5, 2021 at 10:22 PM David Faure wrote:
> > > For frameworks, I think we should be able to write a one-time script
> that
> > > generates .kde-ci.yml files using the
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 the
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 R
How do we get a visual on exactly which lines are covered by auto testing
and which aren't?
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 trans
On dimanche 5 septembre 2021 12:26:50 CEST Ben Cooksley wrote:
> On Sun, Sep 5, 2021 at 10:22 PM David Faure wrote:
> > For frameworks, I think we should be able to write a one-time script that
> > generates .kde-ci.yml files using the dependencies listed in kde-build-
> > metadata (and the platfo
On Sun, Sep 5, 2021 at 10:22 PM David Faure wrote:
> On dimanche 5 septembre 2021 12:11:05 CEST Ben Cooksley wrote:
> > It would be appreciated if people could please work on getting these
> files
> > populated in Frameworks (as everyone needs those) as well as in their own
> > repositories as th
On dimanche 5 septembre 2021 12:11:05 CEST Ben Cooksley wrote:
> It would be appreciated if people could please work on getting these files
> populated in Frameworks (as everyone needs those) as well as in their own
> repositories as they are required before we can proceed much further.
Like this
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 b
On Sun, Sep 5, 2021 at 9:04 PM Gilles Caulier
wrote:
> Congratulations to Ben for this important step in the KDE CI workflow.
>
> I'm sure that it's too far ahead, but we will be interested later, when
> the infrastructure is ready in gitlab, to run all gitlab CI with digiKam
> code. Of course th
Congratulations to Ben for this important step in the KDE CI workflow.
I'm sure that it's too far ahead, but we will be interested later, when the
infrastructure is ready in gitlab, to run all gitlab CI with digiKam code.
Of course this requires solving a lot of dependencies, but please keep in
mi
On zondag 5 september 2021 08:13:09 CEST 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).
>
Yay!
Ha
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.
23 matches
Mail list logo
