-
Improvement
-
Resolution: Won't Do
-
Minor
-
None
We're heavy users of GitVersion to generate version numbers for libraries, which depends on tags in most cases. The switch to the default behavior in the 3.4.0 Git plugin of not fetching tags means that, upon upgrade to 3.4.0 or newer, we'll have to reconfigure every GitVersion-dependent job – dozens, in our case – to add the "Advanced Clone Behaviours" or else they will build incorrectly. There's no way to do this ahead of time (e.g., on Git 3.3.2), so it's a disruptive change.
It would be great to have a global Jenkins switch to enable the previous behavior – fetching tags by default, for backwards compatibility – or, if feasible, to have any existing pipeline jobs (at the point of the 3.4.0+ upgrade) initialize with this Advanced Clone Behaviours config added (leaving it to job maintainers to remove as they see fit), with only newly added jobs initializing without it.