What is the status for MacOS builds?

Jan 9, 2022 4:34:38 AM Ben Cooksley <bcooks...@kde.org>:

> Hi all,
> 
> Over the past week substantial work has meant that we now have a successfully 
> compiling seed job for Frameworks on Windows under Gitlab.
> 
> This is a significant step on the road to announcing general availability for 
> Windows CI, which I expect projects that use Frameworks only should be able 
> to begin enabling in the coming week (there are a few finishing touches i'd 
> like to make first)
> 
> If your project makes use of Windows CI currently (or would like to begin 
> doing so) and has non-Frameworks dependencies it would be appreciated if you 
> could please reply with a list of those KDE projects you use so we can keep 
> them in mind while working on the seed jobs for Independent Releases and 
> Release Service.
> 
> Following this we will be able to make Windows CI generally available on 
> Gitlab for projects to adopt as needed, and as this represents the migration 
> of the final platform over to Gitlab this will also come with an EOL 
> announcement for build.kde.org[http://build.kde.org] and it's corresponding 
> infrastructure.
> 
> If your project has not yet migrated to Gitlab native CI for any platform 
> then you should do so *immediately* and without delay. Projects making use of 
> legacy jobs on Gitlab (which will have references to sysadmin/ci-tooling 
> instead of sysadmin/ci-utilities and will not have a .kde-ci.yml file) are 
> not using Gitlab native CI and need to take action.
> 
> If you have tooling which interacts with resources provided by 
> build.kde.org[http://build.kde.org] (including 
> build-artifacts.kde.org[http://build-artifacts.kde.org] and the repository 
> sysadmin/ci-tooling) then please contact Sysadmin as soon as possible so we 
> can discuss what the best steps are for you to minimize disruption. My 
> understanding is that this includes apps.kde.org[http://apps.kde.org] as well 
> as the Android SDK Docker image.
> 
> Following the completion of this the dependency metadata located in 
> sysadmin/repo-metadata should be considered unmaintained and no longer in 
> use. We will remove this information in due course to ensure only a single 
> source of truth (being the .kde-ci.yml files now included in repositories). 
> It is expected that this will require updates to kdesrc-build.
> 
> Should anyone have any questions on the above please let us know.
> 
> Thanks,
> Ben Cooksley
> KDE Sysadmin

Reply via email to