Pin git client plugin 3.12.4 for Jenkins 2.332.x tests

[MarkEWaite]

Pin git client plugin 3.12.4 for Jenkins 2.332.x tests

https://issues.jenkins.io/browse/JENKINS-70174 notes that the git client plugin automated tests failed when using a shallow clone (depth == 1) of a single branch. The issue was fixed for Jenkins 2.346.3 and newer with the release of git client plugin 3.13.1. This release is a backport of that fix.

No plugin functionality was changed in this release. It changes the automated tests when run from a shallow clone (depth == 1) of a single branch.

#1613 is the key consumer in the plugin bill of materials.

jenkinsci/plugin-compat-tester#382 is the key consumer in the plugin compatibility tester.

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

@olamy and @jglick I believe we'll need a release of the bom that includes this update.

[MarkEWaite]

@jglick I've labelled this pull request as enhancement so that it will result in a new release of the bom. I think the other updates since the last BOM release justify a new release. Those updates include:

• d16fce9 Bump plugin parent POM from 4.51 to 4.53 in /sample-plugin #1642
• 0401bcc Upgrade HPI plugin from 3.37 to 3.38 #1634
• 7f2e4f5 Bump jenkins.version from 2.381 to 2.382 for bom-weekly #1644
• eec30f7 Bump display-url-api from 2.3.6 to 2.3.7 in /bom-weekly #1639
• 9d47aa9 Bump saml from 4.372.v89f13e4c9e97 to 4.385.v4dea_91565e9d in /bom-weekly #1640
• 7f9f7b8 Bump git-plugin.version from 4.14.1 to 4.14.3 in /bom-weekly #1638
• 538a625 Bump script-security from 1218.v39ca_7f7ed0a_c to 1228.vd93135a_2fb_25 in /bom-weekly #1636

If you don't feel that those pull requests justify a release, could you remove the enhancement label from this pull request so that it does not trigger the release?

[timja]

release whenever you feel like it @MarkEWaite. Generally we release when either there's something we want out there or after a few changes are merged (which sometimes builds up a bit if we forget to trigger a release)

[jglick]

Exactly. We set up CD to make it painless to release any time we even think it might be useful, and jenkinsci/archetypes#488 so that most plugin maintainers should not care anyway.