Actions
Support #13871
open
please tag git revisions that result in deployed packages for -dev streams
Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Description
The main versions are tagged in git (e.g. current release version `1.1.4`). However, package versions on the -dev deployment streams (such as xenial-dev) are not tagged. This means every time we need to figure out what source code corresponds to our build we need to go trawling through the commit log to find a matching date. It would be helpful if the package deployment included a step which tagged the github repo with the version of the built dev package (e.g. `1.1.4.20180524153119`).
Updated by Joshua Randall over 6 years ago
This should also mean that you could do a `git describe` and get something actually related to the corresponding release version, as opposed to `1.1.4-283-g1275e30`
Updated by
Actions