Skip to content
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

Fixing maven artifacts for 1.1 #703

Merged
merged 3 commits into from
Oct 7, 2021

Conversation

dblock
Copy link
Member

@dblock dblock commented Oct 6, 2021

@dblock dblock marked this pull request as draft October 6, 2021 17:36
@dblock dblock marked this pull request as ready for review October 6, 2021 18:27
@dblock dblock force-pushed the build-1.1-scripts branch from e4e869d to 9aca227 Compare October 6, 2021 19:54
Comment on lines -62 to -65

mkdir -p $OUTPUT/maven/org/opensearch
./gradlew publishToMavenLocal -Dopensearch.version=$VERSION -Dbuild.snapshot=$SNAPSHOT
cp -r ~/.m2/repository/org/opensearch/performanceanalyzer-rca $OUTPUT/maven/org/opensearch
Copy link
Member

@saratvemulapalli saratvemulapalli Oct 6, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand this correctly: This would mean we are not going to publish maven artifacts for Perf-analyzer and Perf-analyzer RCA.
Is the product team ok with it?
cc: @elfisher @stockholmux @ahopp

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either way we have already released 1.1 so we cannot go and make changes in the artifacts or we'll end up with different ones in maven than what we've released. The only question now is whether these become part of 1.2, or some earlier patch release.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. For 1.2 may lets create an issues for both of these components to onboard if they'd like to have maven artifacts published. This would be lost when we look few weeks from now.

Also this makes me think, we have to automate verifying maven artifacts are published and have the right signatures for every release, make sure all components we expect exist.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an issue on that, #700

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Zero problems with this @saratvemulapalli.

@dblock dblock merged commit d4c7f3e into opensearch-project:main Oct 7, 2021
@dblock dblock deleted the build-1.1-scripts branch October 7, 2021 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Maven 1.1.0 failed Central Sync due to multiple errors
4 participants