Re: Gitlab CI Dashboards and retirement of build.kde.org

[Ben Cooksley]

On Sun, Sep 4, 2022 at 7:54 AM Johnny Jazeix  wrote:

>
>
> Le sam. 3 sept. 2022 à 21:28, Ben Cooksley  a écrit :
>
>> On Sat, Sep 3, 2022 at 9:29 PM Gleb Popov <6year...@gmail.com> wrote:
>>
>>> On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley  wrote:
>>> >
>>> > As previously indicated, I have now shutdown build.kde.org along with
>>> the domain that supported it's version of the CI tooling.
>>> > The repository containing that tooling has now also been archived, and
>>> the former build.kde.org domain has been redirected to metrics.kde.org.
>>> >
>>> > The server which was acting as a builder for build.kde.org will be
>>> rebuilt in the coming days and reallocated to support Gitlab CI workloads.
>>> >
>>> > Thanks,
>>> > Ben
>>>
>>> What should be used instead of binary-factory? How do I transform this
>>> link?
>>>
>>>
>>> https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe
>>
>>
>> At this time the Binary Factory is not impacted by this.
>>
>> Regards,
>> Ben
>>
>
> Hi,
>
> I think the issue mentioned by Glen is that this link (and all other
> artifacts from binary-factory) is redirected to
> https://build-artifacts.kde.org/binary-factory/Kate_Release_win64/1762/kate-22.08.0-1762-windows-msvc2019_64-cl.exe
> which does not exist.
>

Oops. That is an oversight on my part - apologies - and has now been
corrected (although the URLs will have changed)

Cheers,
Ben


>
>
> Cheers,
> Johnny
>

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Johnny Jazeix]

Le sam. 3 sept. 2022 à 21:28, Ben Cooksley  a écrit :

> On Sat, Sep 3, 2022 at 9:29 PM Gleb Popov <6year...@gmail.com> wrote:
>
>> On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley  wrote:
>> >
>> > As previously indicated, I have now shutdown build.kde.org along with
>> the domain that supported it's version of the CI tooling.
>> > The repository containing that tooling has now also been archived, and
>> the former build.kde.org domain has been redirected to metrics.kde.org.
>> >
>> > The server which was acting as a builder for build.kde.org will be
>> rebuilt in the coming days and reallocated to support Gitlab CI workloads.
>> >
>> > Thanks,
>> > Ben
>>
>> What should be used instead of binary-factory? How do I transform this
>> link?
>>
>>
>> https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe
>
>
> At this time the Binary Factory is not impacted by this.
>
> Regards,
> Ben
>

Hi,

I think the issue mentioned by Glen is that this link (and all other
artifacts from binary-factory) is redirected to
https://build-artifacts.kde.org/binary-factory/Kate_Release_win64/1762/kate-22.08.0-1762-windows-msvc2019_64-cl.exe
which does not exist.

Cheers,
Johnny

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Ben Cooksley]

On Sun, Sep 4, 2022 at 2:13 AM Michael Reeves  wrote:

> I now have no way to even test macosx builds for kdiff3, I have no access
> to a 64bit Intel mac. What are the plans for this and Windows
> builds. I have a functional windows based craft installed locally.
>

At this time the Binary Factory is unaffected by these changes, however
steps will be made in the coming weeks/months to migrate away from the
Binary Factory to equivalent Gitlab jobs (although they won't be available
for Merge Requests due to various technical limitations)

Regards,
Ben


>
>
> Sep 3, 2022 12:47:06 AM Ben Cooksley :
>
> On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley  wrote:
>
>> Hi all,
>>
>> This evening I completed the necessary setup required to complete our
>> Gitlab CI dashboards, which can now be found at
>> https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE Developer
>> account login required)
>>
>> These allow any developer to get a view on the current CI status of
>> projects and groups of projects on a branch and platform basis - and should
>> hopefully provide useful insight into the overall status that can currently
>> be obtained from Jenkins.
>>
>> As this was the last thing holding us back from shutting down
>> build.kde.org, i'd like to proceed with retiring and shutting down
>> build.kde.org as soon as possible so the capacity it occupies can be
>> released and reallocated to Gitlab.
>>
>
> As previously indicated, I have now shutdown build.kde.org along with the
> domain that supported it's version of the CI tooling.
> The repository containing that tooling has now also been archived, and the
> former build.kde.org domain has been redirected to metrics.kde.org.
>
> The server which was acting as a builder for build.kde.org will be
> rebuilt in the coming days and reallocated to support Gitlab CI workloads.
>
>
>>
>> If anyone would like to experiment with customised views for their own
>> purposes (where the above provided ones are insufficient) please file a
>> Sysadmin ticket.
>>
>> Please let me know if there are any questions on the above.
>>
>> Thanks,
>> Ben
>>
>
> Thanks,
> Ben
>
>

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Ben Cooksley]

On Sat, Sep 3, 2022 at 9:29 PM Gleb Popov <6year...@gmail.com> wrote:

> On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley  wrote:
> >
> > As previously indicated, I have now shutdown build.kde.org along with
> the domain that supported it's version of the CI tooling.
> > The repository containing that tooling has now also been archived, and
> the former build.kde.org domain has been redirected to metrics.kde.org.
> >
> > The server which was acting as a builder for build.kde.org will be
> rebuilt in the coming days and reallocated to support Gitlab CI workloads.
> >
> > Thanks,
> > Ben
>
> What should be used instead of binary-factory? How do I transform this
> link?
>
>
> https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe


At this time the Binary Factory is not impacted by this.

Regards,
Ben

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Nicolas Fella]

Only build.kde.org is shut down, binary-factory.kde.org is unaffected

On 9/3/22 16:12, Michael Reeves wrote:

I now have no way to even test macosx builds for kdiff3, I have no
access to a 64bit Intel mac. What are the plans for this and Windows
builds. I have a functional windows based craft installed locally.

Sep 3, 2022 12:47:06 AM Ben Cooksley :

On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley 
wrote:

Hi all,

This evening I completed the necessary setup required to
complete our Gitlab CI dashboards, which can now be found at
https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE
Developer account login required)

These allow any developer to get a view on the current CI
status of projects and groups of projects on a branch and
platform basis - and should hopefully provide useful insight
into the overall status that can currently be obtained from
Jenkins.

As this was the last thing holding us back from shutting down
build.kde.org , i'd like to proceed with
retiring and shutting down build.kde.org
 as soon as possible so the capacity it
occupies can be released and reallocated to Gitlab.


As previously indicated, I have now shutdown build.kde.org
 along with the domain that supported it's
version of the CI tooling.
The repository containing that tooling has now also been archived,
and the former build.kde.org  domain has
been redirected to metrics.kde.org .

The server which was acting as a builder for build.kde.org
 will be rebuilt in the coming days and
reallocated to support Gitlab CI workloads.


If anyone would like to experiment with customised views for
their own purposes (where the above provided ones are
insufficient) please file a Sysadmin ticket.

Please let me know if there are any questions on the above.

Thanks,
Ben


Thanks,
Ben

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Michael Reeves]

I now have no way to even test macosx builds for kdiff3, I have no access to a 
64bit Intel mac. What are the plans for this and Windows
builds. I have a functional windows based craft installed locally.

Sep 3, 2022 12:47:06 AM Ben Cooksley :

> On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley  wrote:
>> Hi all,
>> 
>> This evening I completed the necessary setup required to complete our Gitlab 
>> CI dashboards, which can now be found at 
>> https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE Developer 
>> account login required)
>> 
>> These allow any developer to get a view on the current CI status of projects 
>> and groups of projects on a branch and platform basis - and should hopefully 
>> provide useful insight into the overall status that can currently be 
>> obtained from Jenkins.
>> 
>> As this was the last thing holding us back from shutting down 
>> build.kde.org[http://build.kde.org], i'd like to proceed with retiring and 
>> shutting down build.kde.org[http://build.kde.org] as soon as possible so the 
>> capacity it occupies can be released and reallocated to Gitlab.
> 
> As previously indicated, I have now shutdown 
> build.kde.org[http://build.kde.org] along with the domain that supported it's 
> version of the CI tooling.
> The repository containing that tooling has now also been archived, and the 
> former build.kde.org[http://build.kde.org] domain has been redirected to 
> metrics.kde.org[http://metrics.kde.org].
> 
> The server which was acting as a builder for 
> build.kde.org[http://build.kde.org] will be rebuilt in the coming days and 
> reallocated to support Gitlab CI workloads.
>  
>> 
>> If anyone would like to experiment with customised views for their own 
>> purposes (where the above provided ones are insufficient) please file a 
>> Sysadmin ticket.
>> 
>> Please let me know if there are any questions on the above.
>> 
>> Thanks,
>> Ben
> 
> Thanks,
> Ben 


signature.asc
Description: PGP signature

Re: Gitlab CI Dashboards and retirement of build.kde.org

[Gleb Popov]

On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley  wrote:
>
> As previously indicated, I have now shutdown build.kde.org along with the 
> domain that supported it's version of the CI tooling.
> The repository containing that tooling has now also been archived, and the 
> former build.kde.org domain has been redirected to metrics.kde.org.
>
> The server which was acting as a builder for build.kde.org will be rebuilt in 
> the coming days and reallocated to support Gitlab CI workloads.
>
> Thanks,
> Ben

What should be used instead of binary-factory? How do I transform this link?

https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe

Re: Eloquens now on KDEREVIEW)

[Tomaz Canabrava]

Hello All,

All discussion was resolved by Felipe in the past few weeks,
I Assume this is done, and should be moved out of KDE Review?

Best.


On Tue, Jun 28, 2022 at 4:54 PM Felipe Kinoshita  wrote:

> friendly ping! :)
>
> On Wed, Jun 22, 2022 at 5:44 PM Felipe Kinoshita 
> wrote:
> >
> > > Ah! I would suggest moving the conversion into the Controller then. As
> > > far as kcfg, your Config object and your Settings.qml are concerned
> > > they can be proper bools, it's only in the Controller that you have
> > > the presentation requirement that bools must be 0/1. This saves you
> > > the two-way conversion, in the Controller you only need to convert
> > > bool=>int and the rest of the app can treat them as proper bools.
> >
> > Indeed, this makes much more sense.
> >
> > Fixed it now!
> >
> > Thanks,
> > Felipe
> >
> > On Wed, Jun 22, 2022 at 10:10 AM Harald Sitter  wrote:
> > >
> > > On Wed, Jun 22, 2022 at 12:07 AM Felipe Kinoshita 
> wrote:
> > > >
> > > > > Could you elaborate why your config.kcfg uses Ints for everything
> when
> > > > > you clearly want booleans (e.g. `Config.code == 1 ? true : false`)
> > > >
> > > > The API expects ones and zeros for its params, I chose to convert
> them to
> > > > booleans to make the API call easier to write and change.
> > >
> > > Ah! I would suggest moving the conversion into the Controller then. As
> > > far as kcfg, your Config object and your Settings.qml are concerned
> > > they can be proper bools, it's only in the Controller that you have
> > > the presentation requirement that bools must be 0/1. This saves you
> > > the two-way conversion, in the Controller you only need to convert
> > > bool=>int and the rest of the app can treat them as proper bools.
> > >
> > > HS
>