[BUILD-665] Switch to a more efficient release plugin Created: 27/Jan/22 Updated: 09/Aug/22 Resolved: 09/Aug/22 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Obsolete | 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
|
||||||||||||
| Epic Link: | Release automation | ||||||||||||
| Description |
|
It takes Maven's release plugin 48 minutes to release UI because it's building it twice. Look into alternatives that would be more efficient, see for instance:
We could also skip tests & Clover when running the release for real. If the tests were successful in dry-run for a given hash, no need to run them again. |