Add the ability to set Metadata filters for all Pipeline environments at once
In order to update the metadata filters in a pipeline, one must individually update each environment's metadata filter from the list of Continuous Integration jobs.
It would be amazing to be able to set a metadata filter in the pipeline and have it propagate to all environments in the pipeline.
The way metadata filters work in CI jobs has been updated. Changes made to a shared custom filter will now apply immediately to all CI jobs where that filter is used. This means a single filter can be used to manage multiple CI jobs. Check our documentation for more information.
To adopt this, head to your CI jobs, select the filter you need, and hit save in all of them.
-
susanoo chidori commented
we have complex pipeline and this would save so much time. Also better that we can version control the filters and can load as well so we have backup of filters that have complex regexes.
-
Conlan commented
+1 definitely! This is something that is recommended during onboarding, and we've run into at least 1 issue where our CI jobs filters became outdated after adding some metadata types to our commonly used team filter, and the change was not propagated to all of our CI Jobs' filters.
This feels like a design flaw, given all the CI jobs in the pipeline must use the same filter, but as an end-user we have to manage the filters in each job to ensure they stay in sync.