-
Notifications
You must be signed in to change notification settings - Fork 438
RATIS-2211. publish-mvn fails with: ... did not assign a file to the build artifact #1190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
szetszwo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 the change looks good.
@OneSizeFitsQuorum , please see if you could take a look at this change.
dev-support/make_rc.sh
Outdated
| } | ||
|
|
||
| publish-mvn(){ | ||
| 3-publish-mvn(){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about move this function to line 124?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left it here to clarify the actual diff.
Sure, we can move it.
OneSizeFitsQuorum
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Thanks @OneSizeFitsQuorum, @szetszwo for the review. |
What changes were proposed in this pull request?
RATIS-2206 introduced a problem in the release process: plain
deploy:deployfails for modules withpackaging=jar. Previous test has not revealed this, because the first module is apom, deployment was attempted, and it was expected to fail due to lack of authentication.It turns out we cannot skip re-build of the project. However, we can reorder steps to ensure items published to Maven and Subversions are consistent.
(Alternatively we could publish files one-by-one using
deploy:deploy-file, but it's error-prone.)I think it is safe to publish to the Maven staging repo before adding files to Subversion locally, since it can be discarded if needed. So the order is now:
prepare-srcverify-bin(renamed fromprepare-binto better reflect its purpose)publish-mvnassemblypublish-gitpublish-svnArtifacts published to Maven and Subversion are both produced by the
publish-mvnstep.Also added numeric prefix to the step names to avoid accidental usage in the old order.
Added
-DdeployAtEnd=trueflag to avoid partially published repo in case any module fails to re-build.https://issues.apache.org/jira/browse/RATIS-2211
How was this patch tested?
Performed release steps. Deployed to local dir, to allow testing full deployment without authentication.