Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
We currently have two preflight checks that compare the outcome of the bundles dependency trees with the changelog to make sure that they are in sync:
- https://git.magnolia-cms.com/projects/INTERNAL/repos/magnolia-mgmt/browse/magnolia-mgmt-app/src/main/java/info/magnolia/mgmt/service/preflight/ReleaseModulesMatchChangelogPreflightCheck.java
- https://git.magnolia-cms.com/projects/INTERNAL/repos/magnolia-mgmt/browse/magnolia-mgmt-app/src/main/java/info/magnolia/mgmt/service/preflight/NoSnapshotIsMissingFromChangelogPreflightCheck.java
They are helpful because this is a recurring release hiccup. However, currently the release task only scans modules' root pom.xml from Bitbucket.. Hence, what may sometimes happen is that there is an inconsistency that needs to be caught by the above preflight checks, but because the submodule's GAV isn't in the in-memory DB, it's ignored.
Acceptance criteria
- test(s) covering actual release hiccups
- PUR 2.7.6 was in CL but 2.5.1 was in bundle because an older demo-projects version imported it, even though PUR 2.7.6 was in CE's pom
- the Bitbucket scanning takes longer because it's looping through all submodules - this is OK, the release has gotten fast lately
Checklists
Acceptance criteria