[BUILD-907] Make relevant preflight checks aware of reactor submodules Created: 19/Sep/22 Updated: 19/Sep/22 |
|
| 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 | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| 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:
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
|