[MRELEASE-1082] Add configuration option for shallow checkout/clone

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M5
• Fix Version/s: 3.0.0-M6
• Component/s: scm
• Labels: checkout clone git shallow up-for-grabs
• Assignee: Michael Osipov
• Reporter: Michael Cramer
• Created: 18/Mar/22 09:48
• Updated: 14/Jun/22 12:44
• Resolved: 07/May/22 17:23

Description

after implementing sonar into our release process we noticed that sonar is complaining about missing blame information

[INFO] [WARNING] Missing blame information for the following files:

I've seen that in MRELEASE-993 this new type of checkout was introduced and it mentions that "per default" the checkout will use the shallow clone. to me, it sounds that this is an option that can be configured, but after taking a look in the code I see that true is hardcoded

i would propose to make this option configurable and have a default of true that can be changed when needed, e.g. in the case during the release sonarqube is called which needs the full history.

Issue Links

• is related to: MRELEASE-1099 Use shallow checkout/clone during release:perform
• relates to: MRELEASE-993 Use shallow checkout per default (git scm)
• links to: GitHub Pull Request #121