<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 10, 2022 at 3:53 AM Michael Reeves <<a href="mailto:reeves.87@gmail.com">reeves.87@gmail.com</a>> wrote:<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> <span dir="ltr" style="font-family:sans-serif;margin-top:0px;margin-bottom:0px">What is the status for MacOS builds?</span></div></blockquote><div><br></div><div>No work is being made on those at this time, in large part because work is focused on getting us off Jenkins currently.</div><div><br></div><div>Regards,</div><div>Ben<br></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"><div>
<br>
<div>
<br>
<div>
<p>Jan 9, 2022 4:34:38 AM Ben Cooksley <<a href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>>:</p>
</div>
<blockquote style="border-left:3px solid rgb(204,204,204);padding-left:3px">
<div dir="ltr">
<div>
Hi all,
</div>
<div>
<br>
</div>
<div>
Over the past week substantial work has meant that we now have a successfully compiling seed job for Frameworks on Windows under Gitlab.
</div>
<div>
<br>
</div>
<div>
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)
</div>
<div>
<br>
</div>
<div>
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.
</div>
<div>
<br>
</div>
<div>
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 <a href="http://build.kde.org" target="_blank">build.kde.org</a> and it's corresponding infrastructure.
</div>
<div>
<br>
</div>
<div>
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.
<br>
</div>
<div>
<br>
</div>
<div>
If you have tooling which interacts with resources provided by <a href="http://build.kde.org" target="_blank">build.kde.org</a> (including <a href="http://build-artifacts.kde.org" target="_blank">build-artifacts.kde.org</a> 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 <a href="http://apps.kde.org" target="_blank">apps.kde.org</a> as well as the Android SDK Docker image.
<br>
</div>
<div>
<br>
</div>
<div>
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.
</div>
<div>
<br>
</div>
<div>
Should anyone have any questions on the above please let us know.
</div>
<div>
<br>
</div>
<div>
Thanks,
</div>
<div>
Ben Cooksley
</div>
<div>
KDE Sysadmin
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote></div></div>