--nextPart1884651.tdWV9SEqCh
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"; protected-headers="v1"
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker@kde.org>
To: kde-core-devel@kde.org
Subject: Re: Retirement of Binary Factory
Date: Mon, 19 Feb 2024 11:39:26 +0100
Message-ID: <4876479.GXAFRqVoOG@daneel>
MIME-Version: 1.0

On Montag, 19. Februar 2024 01:22:32 CET Harald Sitter wrote:
> On Sun, Feb 18, 2024 at 10:23=E2=80=AFAM Ben Cooksley <bcooksley@kde.org>=
 wrote:
> > On Sun, Feb 18, 2024 at 2:58=E2=80=AFPM Loren Burkholder=20
<computersemiexpert@outlook.com> wrote:
> >> Just last evening, I was downloading Filelight on a Windows machine. D=
ue
> >> to the machine being rather ancient and slow, I ended up going for the
> >> direct binary download instead of the Microsoft Store download. The
> >> apps.kde.org page had me download from a Binary Factory link. As of
> >> right now, that link is still on https://apps.kde.org/filelight/, but =
it
> >> obviously doesn't work. I haven't checked the apps.kde.org source, but
> >> it seems that perhaps those URLs are automatically generated for each
> >> app, so it should be trivial to change or remove them.>=20
> > It would appear that Filelight has not yet enabled themselves for any f=
orm
> > of continuous delivery builds aside from Flatpak. See
> > https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml=
?r
> > ef_type=3Dheads
> >=20
> > If Filelight contributors are still interested in supporting other
> > platforms those builds will need to be added.
>
> I'm curious, why didn't you enable stuff for the things that were
> previously building on binary factory?

I have added the Windows jobs to the stable release branch of filelight (an=
d of=20
other projects creating APPX packages).

I haven't (yet?) added Windows jobs to the master branches (or the 24.02=20
branches) of the 95 projects that were doing Windows builds on BF. Help is=
=20
appreciated. Ideally by the project maintainers because they will have to c=
are=20
for the builds and it would therefore be good if they knew how the new stuf=
f is=20
configured.

And it would be good if somebody smoke-tested the Windows builds so that we=
=20
don't waste CI/CD resources for builds that don't work.

Regards,
Ingo

--nextPart1884651.tdWV9SEqCh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZdMv3gAKCRCxb1mVFkdK
usmSAQCTzY3Ter89sxwblOs5FIBU9yA8v5oY0kQ42vgZnz3cDAD8DSwgFpzVrlsx
e5nIr+0ESc1eteJ+HhYIIioIz6PO6g8=
=ZaUp
-----END PGP SIGNATURE-----

--nextPart1884651.tdWV9SEqCh--