-
Notifications
You must be signed in to change notification settings - Fork 278
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
Check maven central distribution requirements #700
Comments
Hey @peternied with existing automation every published jar has .md5, .sha1, sha256, sha512 and .asc extension it has sources and javadoc jar as well Pom extensions for jar and zip are customizable Thank you |
@prudhvigodithi This issue was opened to make sure those requirements are enforced before being uploaded to maven - if not fail with an appropriate error message. I think this issue is still relevant, what do you think? |
@peternied the requirements are already deep in the automation, I'm fine to have an extra workflow/checks to ensure those are there, but if a team want to have a new POM XML extension there are chances the workflow has to be extended, also not always sources and javadoc jar are required, its up to the team (to remove the the shadow jars), I'm open for a discussion on this, Adding @dblock @bbarani @peterzhuamazon @gaiksaya @zelinh |
Closing this issue as it will be tracked via #2928 |
Follow up from #699
At the end of the release process we were surprised by some checks that failed, we should make sure these checks can be enforced before we are in the middle of a release or at least have a best effort to minimize these issues.
Add a check next to https://github.com/opensearch-project/opensearch-build/tree/main/bundle-workflow/src/build_workflow/opensearch that verifies that:
The text was updated successfully, but these errors were encountered: