Re: Retirement of Binary Factory
On Montag, 19. Februar 2024 01:22:32 CET Harald Sitter wrote: > On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley wrote: > > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder wrote: > >> 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?r > > ef_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? I have added the Windows jobs to the stable release branch of filelight (and of other projects creating APPX packages). I haven't (yet?) added Windows jobs to the master branches (or the 24.02 branches) of the 95 projects that were doing Windows builds on BF. Help is appreciated. Ideally by the project maintainers because they will have to care for the builds and it would therefore be good if they knew how the new stuff is configured. And it would be good if somebody smoke-tested the Windows builds so that we don't waste CI/CD resources for builds that don't work. Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: Retirement of Binary Factory
On Mon, Feb 19, 2024 at 1:22 PM Harald Sitter wrote: > On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley wrote: > > > > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder < > computersemiexp...@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 > 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 wrote: > > > > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder < > computersemiexp...@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 > 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 >
Re: Retirement of Binary Factory
On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley wrote: > > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder > 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 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? On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley wrote: > > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder > 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 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
Re: Retirement of Binary Factory
On Sonntag, 18. Februar 2024 10:23:37 CET Ben Cooksley wrote: > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder < > computersemiexp...@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 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 KMyMoney fixed with https://invent.kde.org/websites/kmymoney-org/-/commit/215b802e > - konversation.kde.org > - krita.org > - okular.kde.org > - plasma-mobile.org > - rkward.kde.org > - umbrello.kde.org Cheers Thomas -- Regards Thomas Baumgart - Windows is not the answer. It's the question. The answer is no! - signature.asc Description: This is a digitally signed message part.
Re: Retirement of Binary Factory
On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder < computersemiexp...@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 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
Re: Retirement of Binary Factory
On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote: > On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley 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. 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. - Loren signature.asc Description: This is a digitally signed message part.
Re: Retirement of Binary Factory
On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley 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
Retirement of Binary Factory
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 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
