[BUILD-586] Improve how the latest changelog is resolved Created: 17/Nov/21  Updated: 23/Nov/21  Resolved: 23/Nov/21

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Release automation

 Description   

Up until now, the release webapp has relied on new changelogs appearing on the top of the following page: https://jira.magnolia-cms.com/secure/ManageFilters.jspa?filterView=search

As Jira doesn't provide APIs to browse filters, the bot instead crawls the page.

However, a recent Jira upgrade now orders changelogs by their popularity, which prevents the whole algorithm from running. It appears that the 6.2.13 CL got popular (5 votes), and that it's going to be a the top at the table until people who have starred it unstar it. A Jira admin can't however remove those stars, nor see whom they belong to.

Another problem is that many old CLs (4.5.x, 5.3.x, etc.) fill up the list. If only relevant filters appeared on that page, then we could probably make sure we would always be able to grab the latest changelog.

Solutions:

  • Jira Cloud has APIs to browse filters, short-term migration not realistic though
  • manually star the latest CL so that it can be found with Jira's API to browse a user's starred filters (cumbersome)
  • clean up unused filters, export them & archive them to Google Drive / S3. Write redirects to the new place (requires ongoing work)
  • discard Jira altogether, create a manual release task to write the current changelog ID so the release-webapp knows it (chosen impl. solution)

Generated at Sun Feb 11 23:43:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.