Done
Details
Assignee
Vadim YalovetsVadim YalovetsReporter
Lenz GrimmerLenz Grimmer(Deactivated)Components
Priority
Medium
Details
Details
Assignee
Vadim Yalovets
Vadim YalovetsReporter
Lenz Grimmer
Lenz Grimmer(Deactivated)Components
Priority
Smart Checklist
Smart Checklist
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
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, @Evgeniy Patlan keeps track of the git revision id during the build process, so we can do this retroactively for previous builds, too.