When using Behavior "Filter by name" it should also consider effectively filtering tags (not only branches)

[rodrigocprates]

What feature do you want to see added?

Our repo has 1300+ tags, which delays the Scan execution everytime it runs.

While using Branch Sources > Behaviors > Discover tags + Filter by name, that's not possible to apply this filter to loaded tags (looks like it's listing all tags using git command) - only filtering branches.

Suggestion would be to either:

• consider tags in "Filter by name (regex/wildcards)" behavior
• create new behaviors such as "Filter by tag name"

I would love to work on this as my first contribution, but I'd definitely need some inputs and orientation on the best approach.

Upstream changes

No response

[calle2010]

As far as I can tell the scan as visible in "Scan Multibranch Pipeline Log" and "Multibranch Pipeline Events" does not take into account the filter for branches either. All branches and tags in our repository are scanned, even though for only a fraction jobs are created because the rest is filtered out. Applying the filters to the scan would help us tremendously because the scanning process already maxes out our HTTP request limit, causing build jobs to fail when they are started in parallel to the scan.