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

List:       kde-core-devel
Subject:    Re: Retirement of Binary Factory
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2024-02-19 10:20:24
Message-ID: CA+XidOEnvtAd4wtfU5XCd3-T=G-zbgaHJjVL0BbgBcPZDFFNWw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Feb 19, 2024 at 1:22 PM Harald Sitter <sitter@kde.org> wrote:

> On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley <bcooksley@kde.org> wrote:
> >
> > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder <
> computersemiexpert@outlook.com> wrote:
> >>
> >> On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote:
> >> > On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley <bcooksley@kde.org>
> wrote:
> >> >
> >> > The Binary Factory, alongside it's two build servers, and the Flatpak
> >> > repository it provided at https://distribute.kde.org/ has now been
> >> > decommissioned.
> >>
> >> Hi all,
> >>
> >> Just last evening, I was downloading Filelight on a Windows machine.
> Due 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.
> >
> >
> > It would appear that Filelight has not yet enabled themselves for any
> form of continuous delivery builds aside from Flatpak.
> > See
> https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads
> >
> > 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?
>

Because in the past what people have done is turn on builds for projects on
the Binary Factory that the underlying projects actually didn't care about
and had little interest in.
That was part of the reason why the Binary Factory was a bit of a
maintainability nightmare - as constant fixes were required for some
projects as they broke builds.

Hence why projects were asked to step up and enable builds themselves.

Cheers,
Ben


>
> On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley <bcooksley@kde.org> wrote:
> >
> > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder <
> computersemiexpert@outlook.com> wrote:
> >>
> >> On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote:
> >> > On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley <bcooksley@kde.org>
> wrote:
> >> >
> >> > The Binary Factory, alongside it's two build servers, and the Flatpak
> >> > repository it provided at https://distribute.kde.org/ has now been
> >> > decommissioned.
> >>
> >> Hi all,
> >>
> >> Just last evening, I was downloading Filelight on a Windows machine.
> Due 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.
> >
> >
> > It would appear that Filelight has not yet enabled themselves for any
> form of continuous delivery builds aside from Flatpak.
> > See
> https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads
> >
> > If Filelight contributors are still interested in supporting other
> platforms those builds will need to be added.
> >
> >>
> >>
> >> Are there other places that need this URL replaced as well?
> https://lxr.kde.org/search?%21v=kf6-qt6&_filestring=&_string=binary-factory.kde.org
> shows that there are a number of READMEs that still link to Binary Factory,
> and Krita has some CI stuff that still references binary-factory.kde.org,
> but I have a sneaking suspicion that there are binary-factory.kde.org
> links in KDE webpages and other repositories that aren't indexed by
> lxr.kde.org.
> >
> >
> > I have a checkout of most website repositories on my local system and
> did a quick grep which showed a variety of hits. Most of them were on
> README files that were intended to show build status of the website itself.
> > Those links would have been broken for some time as websites were
> converted over a while ago.
> >
> > Affected sites content wise includes:
> > - develop.kde.org
> > - digikam.org
> > - haruna.kde.org
> > - kaidan.im
> > - kate-editor.org
> > - kdeconnect.kde.org
> > - kde.ru
> > - kdevelop.org
> > - kirogi.org
> > - kmymoney.org
> > - konversation.kde.org
> > - krita.org
> > - okular.kde.org
> > - plasma-mobile.org
> > - rkward.kde.org
> > - umbrello.kde.org
> >
> >
> >>
> >>
> >> - Loren
> >
> >
> > Cheers,
> > Ben
>

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Mon, Feb 19, 2024 at 1:22 PM 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">On Sun, Feb 18, 2024 \
at 10:23 AM Ben Cooksley &lt;<a href="mailto:bcooksley@kde.org" \
target="_blank">bcooksley@kde.org</a>&gt; wrote:<br> &gt;<br>
&gt; On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder &lt;<a \
href="mailto:computersemiexpert@outlook.com" \
target="_blank">computersemiexpert@outlook.com</a>&gt; wrote:<br> &gt;&gt;<br>
&gt;&gt; On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote:<br>
&gt;&gt; &gt; On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley &lt;<a \
href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>&gt; wrote:<br> \
&gt;&gt; &gt;<br> &gt;&gt; &gt; The Binary Factory, alongside it&#39;s two build \
servers, and the Flatpak<br> &gt;&gt; &gt; repository it provided at <a \
href="https://distribute.kde.org/" rel="noreferrer" \
target="_blank">https://distribute.kde.org/</a> has now been<br> &gt;&gt; &gt; \
decommissioned.<br> &gt;&gt;<br>
&gt;&gt; Hi all,<br>
&gt;&gt;<br>
&gt;&gt; Just last evening, I was downloading Filelight on a Windows machine. Due to \
the machine being rather ancient and slow, I ended up going for the direct binary \
download instead of the Microsoft Store download. The <a href="http://apps.kde.org" \
rel="noreferrer" target="_blank">apps.kde.org</a> page had me download from a Binary \
Factory link. As of right now, that link is still on <a \
href="https://apps.kde.org/filelight/" rel="noreferrer" \
target="_blank">https://apps.kde.org/filelight/</a>, but it obviously doesn&#39;t \
work. I haven&#39;t checked the <a href="http://apps.kde.org" rel="noreferrer" \
target="_blank">apps.kde.org</a> source, but it seems that perhaps those URLs are \
automatically generated for each app, so it should be trivial to change or remove \
them.<br> &gt;<br>
&gt;<br>
&gt; It would appear that Filelight has not yet enabled themselves for any form of \
continuous delivery builds aside from Flatpak.<br> &gt; See <a \
href="https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads" \
rel="noreferrer" target="_blank">https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads</a><br>
 &gt;<br>
&gt; If Filelight contributors are still interested in supporting other platforms \
those builds will need to be added.<br> <br>
I&#39;m curious, why didn&#39;t you enable stuff for the things that were<br>
previously building on binary factory?<br></blockquote><div><br></div><div>Because in \
the past what people have done is turn on builds for projects on the Binary Factory \
that the underlying projects actually didn&#39;t care about and had little interest \
in.</div><div>That was part of the reason why the Binary Factory was a bit of a \
maintainability nightmare - as constant fixes were required for some projects as they \
broke builds.</div><div><br></div><div>Hence why projects were asked to step up and \
enable builds themselves.</div><div><br></div><div>Cheers,</div><div>Ben</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> <br>
On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley &lt;<a \
href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>&gt; wrote:<br> \
&gt;<br> &gt; On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder &lt;<a \
href="mailto:computersemiexpert@outlook.com" \
target="_blank">computersemiexpert@outlook.com</a>&gt; wrote:<br> &gt;&gt;<br>
&gt;&gt; On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote:<br>
&gt;&gt; &gt; On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley &lt;<a \
href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>&gt; wrote:<br> \
&gt;&gt; &gt;<br> &gt;&gt; &gt; The Binary Factory, alongside it&#39;s two build \
servers, and the Flatpak<br> &gt;&gt; &gt; repository it provided at <a \
href="https://distribute.kde.org/" rel="noreferrer" \
target="_blank">https://distribute.kde.org/</a> has now been<br> &gt;&gt; &gt; \
decommissioned.<br> &gt;&gt;<br>
&gt;&gt; Hi all,<br>
&gt;&gt;<br>
&gt;&gt; Just last evening, I was downloading Filelight on a Windows machine. Due to \
the machine being rather ancient and slow, I ended up going for the direct binary \
download instead of the Microsoft Store download. The <a href="http://apps.kde.org" \
rel="noreferrer" target="_blank">apps.kde.org</a> page had me download from a Binary \
Factory link. As of right now, that link is still on <a \
href="https://apps.kde.org/filelight/" rel="noreferrer" \
target="_blank">https://apps.kde.org/filelight/</a>, but it obviously doesn&#39;t \
work. I haven&#39;t checked the <a href="http://apps.kde.org" rel="noreferrer" \
target="_blank">apps.kde.org</a> source, but it seems that perhaps those URLs are \
automatically generated for each app, so it should be trivial to change or remove \
them.<br> &gt;<br>
&gt;<br>
&gt; It would appear that Filelight has not yet enabled themselves for any form of \
continuous delivery builds aside from Flatpak.<br> &gt; See <a \
href="https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads" \
rel="noreferrer" target="_blank">https://invent.kde.org/utilities/filelight/-/blob/master/.gitlab-ci.yml?ref_type=heads</a><br>
 &gt;<br>
&gt; If Filelight contributors are still interested in supporting other platforms \
those builds will need to be added.<br> &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Are there other places that need this URL replaced as well? <a \
href="https://lxr.kde.org/search?%21v=kf6-qt6&amp;_filestring=&amp;_string=binary-factory.kde.org" \
rel="noreferrer" target="_blank">https://lxr.kde.org/search?%21v=kf6-qt6&amp;_filestring=&amp;_string=binary-factory.kde.org</a> \
shows that there are a number of READMEs that still link to Binary Factory, and Krita \
has some CI stuff that still references <a href="http://binary-factory.kde.org" \
rel="noreferrer" target="_blank">binary-factory.kde.org</a>, but I have a sneaking \
suspicion that there are <a href="http://binary-factory.kde.org" rel="noreferrer" \
target="_blank">binary-factory.kde.org</a> links in KDE webpages and other \
repositories that aren&#39;t indexed by <a href="http://lxr.kde.org" rel="noreferrer" \
target="_blank">lxr.kde.org</a>.<br> &gt;<br>
&gt;<br>
&gt; I have a checkout of most website repositories on my local system and did a \
quick grep which showed a variety of hits. Most of them were on README files that \
were intended to show build status of the website itself.<br> &gt; Those links would \
have been broken for some time as websites were converted over a while ago.<br> \
&gt;<br> &gt; Affected sites content wise includes:<br>
&gt; - <a href="http://develop.kde.org" rel="noreferrer" \
target="_blank">develop.kde.org</a><br> &gt; - <a href="http://digikam.org" \
rel="noreferrer" target="_blank">digikam.org</a><br> &gt; - <a \
href="http://haruna.kde.org" rel="noreferrer" target="_blank">haruna.kde.org</a><br> \
&gt; - <a href="http://kaidan.im" rel="noreferrer" target="_blank">kaidan.im</a><br> \
&gt; - <a href="http://kate-editor.org" rel="noreferrer" \
target="_blank">kate-editor.org</a><br> &gt; - <a href="http://kdeconnect.kde.org" \
rel="noreferrer" target="_blank">kdeconnect.kde.org</a><br> &gt; - <a \
href="http://kde.ru" rel="noreferrer" target="_blank">kde.ru</a><br> &gt; - <a \
href="http://kdevelop.org" rel="noreferrer" target="_blank">kdevelop.org</a><br> &gt; \
- <a href="http://kirogi.org" rel="noreferrer" target="_blank">kirogi.org</a><br> \
&gt; - <a href="http://kmymoney.org" rel="noreferrer" \
target="_blank">kmymoney.org</a><br> &gt; - <a href="http://konversation.kde.org" \
rel="noreferrer" target="_blank">konversation.kde.org</a><br> &gt; - <a \
href="http://krita.org" rel="noreferrer" target="_blank">krita.org</a><br> &gt; - <a \
href="http://okular.kde.org" rel="noreferrer" target="_blank">okular.kde.org</a><br> \
&gt; - <a href="http://plasma-mobile.org" rel="noreferrer" \
target="_blank">plasma-mobile.org</a><br> &gt; - <a href="http://rkward.kde.org" \
rel="noreferrer" target="_blank">rkward.kde.org</a><br> &gt; - <a \
href="http://umbrello.kde.org" rel="noreferrer" \
target="_blank">umbrello.kde.org</a><br> &gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; - Loren<br>
&gt;<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Ben<br>
</blockquote></div></div>



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

Configure | About | News | Add a list | Sponsored by KoreLogic