[BUILD-867] Generate the Maven sites based on DynamoDB records rather than Jenkins build history Created: 07/Jul/22 Updated: 24/Apr/23 |
|
| Status: | Selected |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
In 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. |