Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
In BUILD-843 the use case we first saw the following use case: access release history from a command (PostReleaseCommand) that isn't ReleaseCommand.
The current approach is that we scan Jenkins builds to reconstruct what got released. However, we should rather store this data in a DB table. That way, we can look it up again cleanly when we need it.
Doing this, we should fetch the list of tags from the release-job itself, rather than using the latest pushed tag on a Bitbucket repository.
Checklists
Acceptance criteria