Closed alambike closed 2 weeks ago
I don't follow this particula label, the tenant label can not interfere in the building decission right? @alambike
Is an example of extra labels that a flavor could have, to try to show that the matchLabel
option should try to find the flavors which match with the labels specified, but other labels can be defined in the flavor configuration.
Use case
Currently, we don't have an option to skip the automatic build of pre-releases when the build_snapshots workflow is triggered, as both elements are classified under the same
image_type
.Option 1: The ugly
To skip this limitation, we could easily add support for fnmatch glob patterns,
So we can use it in the
build_images
workflow automatic invocation, to filter by an agreed pattern:https://github.com/prefapp/features/blob/main/packages/build_images/templates/.github/workflows/build_snapshots.yaml#L38
Option 2: The good
Instead of try to agree with a flavor naming convention with the developer team, we could use flavor labels, based on the
github.event_name
and types. For example, to configure the build of my flavor on pre-release events, I have to configure:And the build-prereleases workflow will have the following call: