Skip to content

Stable branch builds should use latest tag on branch

Stable branch builds should use latest tag on branch

Builds on the stable branch should compute the GitLab version using
the latest tag associated with the branch.

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6843

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

What does this MR do?

When on stable branches, do not use the latest tag (which might be newer than the tag associated with stable branch), but use the latest one associated to that stable branch.

Related issues

Closes #6843 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by Robert Marshall

Merge request reports