[BUILD-634] Decouple release notes automation (cool down) from the release process Created: 10/Jan/22 Updated: 14/Jan/22 Resolved: 14/Jan/22 |
|
| 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 |
|
In order to not deal with an all-encompassing release process that would both do the release and the release notes, one possible solution is to introduce a separate cron job. It would keep an eye on Nexus for new dx-core releases, and only trigger then. Use the following endpoint: https://nexus.magnolia-cms.com/service/local/repositories/magnolia.enterprise.releases/content/info/magnolia/dx/magnolia-dx-core-installer/6.2.4/magnolia-dx-core-installer-6.2.4.jar?describe=info This would allow us to test that part of the process more easily, as we wouldn't depend on a Magnolia release. |