-
Notifications
You must be signed in to change notification settings - Fork 276
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
[Bug] Maven 1.1.0 failed Central Sync due to multiple errors #699
Comments
We should not be publishing job-scheduler, only SPI, that fix would be to remove https://github.com/opensearch-project/opensearch-build/blob/main/bundle-workflow/scripts/components/job-scheduler/build.sh#L63 |
Existing issues have been resolved but release was stopped with this error:
|
@peternied pls recap all the manual steps you did to unblock opensearch-1007 #close |
Script to generate missing checksums,
Note: This is documentation of the process used for this release, not what we should do and many of these steps have already been mitigated with other issues resolved in this and component repositories Prereqs:
Remediation steps:
Deploy Artifacts
|
This was fixed in opensearch-project/job-scheduler#71 and #703
The maven-metadata-local.xml comes from publishing to ~/.m2, and it's being removed when we publish via
Fixed as above.
Where do we see one in the build today? I can't find any. |
While the |
I did not attempt to remove the file. Do we need the maven-metadata.xml at all, if not, we can alter the publishing process to filter them out before starting. Tracking with #713 |
Describe the bug
[Bug] Maven 1.1.0 failed Central Sync due to multiple errors.
When we try to release Maven Artifacts for 1.1.0 OpenSearch to Maven Central through sonatype, we encounter these errors that block us from closing.
Here are all the issues we see:
Event: Failed: Javadoc Validation:
Event: Failed: Checksum Validation:
Event: Failed: POM Validation:
Event: Failed: Sources Validation:
Because of these errors, we are not able to close the repo, and proceed to publish the 1.1.0 release in Maven Central.
In 1.0.0, @peternied and @mch2 have removed PA in order to complete the release.
This time we are seeing more errors coming from plugin specifically.
Thanks.
To reproduce
See above.
Expected behavior
Click Close in Sonatype should close the repo.
Screenshots
Error screenshot:
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: