orchestrator: Apply git tags to track our release builds

Description

When releasing packages derived from our local git repository of MySQL orchestrator, we currently stick to the last upstream version number (3.2.6) and append a build number using a dash, e.g. 3.2.6-3. In order to keep track of the git revision that was used to perform such a release build, we should apply tags to the corresponding git revision. To my knowledge, keeps track of the git revision id during the build process, so we can do this retroactively for previous builds, too.

Environment

None

Attachments

2
  • 09 Aug 2022, 01:57 PM
  • 04 Aug 2022, 02:36 PM

Smart Checklist

Activity

Vadim Yalovets August 4, 2022 at 2:36 PM

Next tags are added: v3.1.4-1, v3.2.4-1, v3.2.5-1, v3.2.6-1, v3.2.6-2, v3.2.6-3

Done

Details

Assignee

Reporter

Priority

Smart Checklist

Created May 3, 2022 at 7:43 AM
Updated March 5, 2024 at 11:14 AM
Resolved August 5, 2022 at 10:41 AM

Flag notifications