On Fri, May 9, 2025 at 10:58 PM Albert Vaca Cintora <albertv...@gmail.com> wrote:
> The macOS jobs are just included from templates, so I can't change them. > But I just discovered that includes can be conditional > <https://docs.gitlab.com/ci/yaml/includes/#use-rules-with-include>, so > I'll give that a try. If you were proposing something else I didn't quite > understand it. > The included jobs can certainly be modified in individual projects .gitlab-ci.yml files - it is just something we discourage. See https://invent.kde.org/websites/krita-org/-/blob/master/.gitlab-ci.yml?ref_type=heads for an example of this. Cheers, Ben > > On Thu, May 8, 2025 at 12:10 PM Ben Cooksley <bcooks...@kde.org> wrote: > >> On Thu, May 8, 2025 at 8:43 AM Ingo Klöcker <kloec...@kde.org> wrote: >> >>> On Mittwoch, 7. Mai 2025 21:22:31 Mitteleuropäische Sommerzeit Albert >>> Vaca >>> Cintora wrote: >>> > I've disabled kdeconnect macOS builds for the release branch. I wonder >>> if >>> > there's a way to never build macOS builds from release branches for KDE >>> > Connect, to save CI resources? We don't make releases from them (we >>> point >>> > macOS users to download builds from master directly) so those builds >>> are >>> > never used. >>> >>> This should be possible by adding different rules to the craft_macos >>> jobs in >>> kdeconnect-kde's .gitlab-ci.yaml. I can have a look, but not tonight. >>> >> >> See line 23 of >> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/blocks/workflow.yml?ref_type=heads#L23 >> The documentation on what is possible is available at >> https://docs.gitlab.com/ci/yaml/#rules and the list of environment >> variables available is at >> https://docs.gitlab.com/ci/variables/predefined_variables/ >> >> >>> >>> Regards, >>> Ingo >> >> >> Cheers, >> Ben >> >
