Disable shallow clones in the build-rpm CI job (!104) · Merge requests · cmsgemonline / gem-daq / cmsgemos · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Laurent Petre requested to merge bugfix/gitlab-ci-rpm-version into develop Feb 11, 2021

Description

Title says it all; here is the commit message for more detailed explanations.

Since tito uses 'git describe' to compute the RPM version, Git shallow
clones cannot be used. Indeed it can lead to inconsistent results if the
clone depth is not large enough.

Setting the Git clone depth to 1, except for the build-rpm job that
performs a full clone.

Related Issue

How Has This Been Tested?

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

My code follows the code style of this project.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have read the CONTRIBUTING document.
I have added tests to cover my changes.
All new and existing tests passed.