Remove release:perform from maven invocation #101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The time taken to build a release has been increasing steadily and I don't expect things to get any better, currently each build takes about 1.5 hours wall time.
The most time consuming parts of the release is running the unit tests, which we should absolutely do. However, they currently they get run at least three times, once during
release:prepare
, again duringrelease:perform
and again when we build themetaconfig
templates.release:prepare
updates the snapshot, tags the git repository, runs the tests and builds packages.release:perform
runs the tests, builds packages and uploads artifacts to the LAL Nexus.My proposal is that we no longer run
release:perform
and therefore do not push artifacts to the LAL Nexus repository during releases. AFAIK we only push thepom
,tar.gz
andrpm
to Nexus: thepom
we also keep in the git repository, therpm
s have the wrong names (and are unsigned) and I am unsure if anyone uses thetar.gz
.Would anything break if we stopped pushing to Nexus? I suspect not.