[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-18 1:35:48
Message-ID: CA+XidOGcP5YwqSGcVbNeN5d+YbMfdiAg85gvWPbou421KKOjLg () mail ! gmail ! com
[Download RAW message or body]
On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley <bcooksley@kde.org> wrote:
> Hi all,
>
> For some time now we have been steadily working on getting our ability to
> build everything that was previously built on the Binary Factory being
> built on Gitlab.
>
> I'm now very happy to advise that it is now possible to perform all of
> those builds on Gitlab (and depending on how far you configure it, go even
> further than what was being done before). This transition to Gitlab builds
> should also ensure we use resources more efficiently, as builds will only
> take place when code actually changes (rather than every day - which is
> what the Binary Factory did).
>
> As such, with Gitlab now able to replace it, I am scheduling the Binary
> Factory for decommissioning in 2 weeks time.
> Projects relying on signed binary builds of their project should therefore
> look into migrating their builds immediately and without delay.
>
The Binary Factory, alongside it's two build servers, and the Flatpak
repository it provided at https://distribute.kde.org/ has now been
decommissioned.
>
> The legacy Flatpak repository at http://distribute.kde.org/ will also be
> retired as part of this. Anyone still using this should migrate to the
> per-application Flatpak repositories at https://cdn.kde.org/flatpak/
> noting that if you are adding the repository directly you may need to add
> the KF6 runtime first.
>
> Redirects will not be provided from the older Binary Factory URLs as there
> is no successor URL for many of the Binary Factory endpoints.
>
> Details on how to setup your project with binary builds can be found at
> https://invent.kde.org/sysadmin/ci-utilities/-/tree/master/gitlab-templates
>
> For enabling signed builds of your project builds please see
> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/signing/README.md.
> Please note that signing is only permitted on mainline repository branches
> marked as protected within Gitlab (which is only done for release branches
> such as master and release/24.04). If your project is missing from the
> configuration please submit a merge request to sysadmin/ci-utilities.
>
> Signing services include publishing Android builds to our F-Droid
> repositories (https://cdn.kde.org/android/), Flatpak repositories (
> https://cdn.kde.org/flatpak/), as well as the staging publishers that
> upload draft submissions to Google Play and the Microsoft Store (for those
> applications using those) - in addition to the actual signing of binaries
> (supported for Linux Flatpak, Android, Windows and Mac).
>
> With regards to macOS, pending fixes in the upstream tooling we use
> (rcodesign) the signing service will also be able to provide notarised
> builds.
> See https://invent.kde.org/sysadmin/ci-notary-service/-/merge_requests/38
> for more information on that.
>
> At this time signing of Appimages to allow use with AppimageUpdate is not
> supported, however to my knowledge this is not used anywhere in KDE outside
> of Krita.
>
> Similarly, work on changing our GItlab configuration to protect tags will
> be needed before we can perform signed builds on tags (see
> https://docs.gitlab.com/ee/user/project/protected_tags.html).
> Based on the documentation this should not be too difficult however so
> i'll add that to the list to look into sooner rather than later (as making
> this change also has implications for the CI system in general)
>
> Thanks,
> Ben
>
>
>
Cheers,
Ben
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr">On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley <<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>> 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"><div dir="ltr">Hi \
all,<div><br></div><div>For some time now we have been steadily working on getting \
our ability to build everything that was previously built on the Binary Factory being \
built on Gitlab.</div><div><br></div><div>I'm now very happy to advise that it is \
now possible to perform all of those builds on Gitlab (and depending on how far you \
configure it, go even further than what was being done before). This transition to \
Gitlab builds should also ensure we use resources more efficiently, as builds will \
only take place when code actually changes (rather than every day - which is what the \
Binary Factory did).</div><div><br></div><div>As such, with Gitlab now able to \
replace it, I am scheduling the Binary Factory for decommissioning in 2 weeks \
time.</div><div>Projects relying on signed binary builds of their project should \
therefore look into migrating their builds immediately and without delay. \
</div></div></blockquote><div><br></div><div>The Binary Factory, alongside it's \
two build servers, and the Flatpak repository it provided at <a \
href="https://distribute.kde.org/">https://distribute.kde.org/</a> has now been \
decommissioned.</div><div> <br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div><div>The legacy \
Flatpak repository at <a href="http://distribute.kde.org/" \
target="_blank">http://distribute.kde.org/</a> will also be retired as part of this. \
Anyone still using this should migrate to the per-application Flatpak repositories at \
<a href="https://cdn.kde.org/flatpak/" \
target="_blank">https://cdn.kde.org/flatpak/</a> noting that if you are adding the \
repository directly you may need to add the KF6 runtime \
first.</div></div><div><br></div><div>Redirects will not be provided from the older \
Binary Factory URLs as there is no successor URL for many of the Binary Factory \
endpoints.</div><div><br></div><div>Details on how to setup your project with binary \
builds can be found at <a \
href="https://invent.kde.org/sysadmin/ci-utilities/-/tree/master/gitlab-templates" \
target="_blank">https://invent.kde.org/sysadmin/ci-utilities/-/tree/master/gitlab-templates</a></div><div><br></div><div>For \
enabling signed builds of your project builds please see <a \
href="https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/signing/README.md" \
target="_blank">https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/signing/README.md</a>. \
Please note that signing is only permitted on mainline repository branches marked as \
protected within Gitlab (which is only done for release branches such as master and \
release/24.04). If your project is missing from the configuration please submit a \
merge request to sysadmin/ci-utilities.</div><div><br></div><div>Signing services \
include publishing Android builds to our F-Droid repositories (<a \
href="https://cdn.kde.org/android/" \
target="_blank">https://cdn.kde.org/android/</a>), Flatpak repositories (<a \
href="https://cdn.kde.org/flatpak/" \
target="_blank">https://cdn.kde.org/flatpak/</a>), as well as the staging publishers \
that upload draft submissions to Google Play and the Microsoft Store (for those \
applications using those) - in addition to the actual signing of binaries (supported \
for Linux Flatpak, Android, Windows and Mac).</div><div><br></div><div>With regards \
to macOS, pending fixes in the upstream tooling we use (rcodesign) the signing \
service will also be able to provide notarised builds.</div><div>See <a \
href="https://invent.kde.org/sysadmin/ci-notary-service/-/merge_requests/38" \
target="_blank">https://invent.kde.org/sysadmin/ci-notary-service/-/merge_requests/38</a> \
for more information on that.</div><div><br></div><div>At this time signing of \
Appimages to allow use with AppimageUpdate is not supported, however to my knowledge \
this is not used anywhere in KDE outside of \
Krita.<br></div><div><br></div><div>Similarly, work on changing our GItlab \
configuration to protect tags will be needed before we can perform signed builds on \
tags (see <a href="https://docs.gitlab.com/ee/user/project/protected_tags.html" \
target="_blank">https://docs.gitlab.com/ee/user/project/protected_tags.html</a>). \
</div><div>Based on the documentation this should not be too difficult however so \
i'll add that to the list to look into sooner rather than later (as making this \
change also has implications for the CI system in \
general)</div><div><br></div><div>Thanks,</div><div>Ben</div><div><br></div><div><br></div></div></blockquote><div><br></div><div>Cheers,</div><div>Ben \
</div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic