Create Task
Maniphest T13884

Enable Kid3 within the Binary Factory
Closed, ResolvedPublic
Actions

Description

At the moment "Kid3_x86_64_flatpak" and "Website_kid3-kde-org" are built with https://binary-factory.kde.org/. I would like to have Windows and macOS packages built too. A craft blueprint is ready at https://invent.kde.org/packaging/craft-blueprints-kde/-/tree/master/extragear/kid3. Maybe it would be sufficient to commit something like the following diff at https://invent.kde.org/sysadmin/binary-factory-tooling. As I have no rights to make a pull request there, I try it with this ticket. Should I do something different instead?

From 5ac48227e734e51af1ea02116604b06ca8365ef8 Mon Sep 17 00:00:00 2001
From: Urs Fleisch <ufleisch@users.sourceforge.net>
Date: Sat, 21 Nov 2020 11:04:49 +0100
Subject: Enable Kid3 within the Binary Factory


diff --git a/craft/enabled-projects.yaml b/craft/enabled-projects.yaml
index 62ed15b..6c63541 100644
--- a/craft/enabled-projects.yaml
+++ b/craft/enabled-projects.yaml
@@ -256,6 +256,14 @@
     target: 'master'
   platforms:
   - 'win64'
+'Kid3':
+  buildBlueprint: "kid3"
+  versions:
+  - name: 'Nightly'
+    target: 'master'
+  platforms:
+  - 'win64'
+  - 'macos'
 'Kig':
   buildBlueprint: "kig"
   versions:
Restricted Application added a subscriber: sysadmin. · View Herald TranscriptNov 21 2020, 10:40 AM
bcooksley closed this task as Resolved.Nov 21 2020, 11:00 AM

What people have usually done with sysadmin/ namespace repos is forked them, made the needed changes and then sent us a Merge Request which we've then reviewed as normal. This is a bit different to how development is normally done (with work branches) but is similar to how the people without a developer account submit their patches.

I've now landed the above patch in https://invent.kde.org/sysadmin/binary-factory-tooling/commit/35229f9c9c8ff8f8169ed4cf03938c1e3bead8a9 and have deployed it on the Binary Factory by running the DSL Job.

I've also triggered the initial run of the jobs.

ufleisch added a comment.Nov 21 2020, 11:17 AM

This was fast, thank you very much! The macOS build failed, I will have a look at the log.