task/WI-351: Allow an explicit Git tag to be passed to Make commands via Jenkins

[jarosenb]

Overview

Currently the Makefile uses git describe on the current branch/tag to determine how to tag Docker images for release. When multiple tags point to the same commit, this can cause the wrong tag to be used.

This PR allows the lookup to be bypassed if the GIT_TAG variable is set upstream by Jenkins. On the Jenkins side, the deploy script has been updated with a $branch_deploy checkbox arg, defaulting to false. Unless it is checked, we run the following code:

if ! $branch_deploy; then
    echo $branch > git_tag.var
fi

This lets deployers opt in to using a branch name to deploy, while the default behavior is to pass the release tag without modification.

Related

• WI-351

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.67%. Comparing base (3d9fb8d) to head (ca37ece).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1194   +/-   ##
=======================================
  Coverage   70.67%   70.67%           
=======================================
  Files         543      543           
  Lines       34129    34129           
  Branches     2843     2843           
=======================================
  Hits        24122    24122           
  Misses       9804     9804           
  Partials      203      203           

Flag	Coverage Δ
javascript	73.00% <ø> (ø)
unittests	60.80% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.