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

Add notifications to 1.0 maven release. #323

Merged
merged 1 commit into from
Aug 25, 2021

Conversation

mch2
Copy link
Member

@mch2 mch2 commented Aug 25, 2021

Signed-off-by: Marc Handalian handalm@amazon.com

Description

Adding notifications to 1.0 maven release.
Updated to build tags and a specific sha of common-utils.

Issues Resolved

Follow up on #307

Check List

  • [ x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@peterzhuamazon
Copy link
Member

Is it notification or notification(s)? It is very inconsistent across this PR.

- name: common-utils
repository: https://github.com/opensearch-project/common-utils.git
ref: 1.0
ref: d05a50e220a239f09a9048a368bc1b698cb7e6bd
Copy link
Member

Choose a reason for hiding this comment

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

Should we create a tag and use that at the SHA?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes that would be great, the existing 1.0.0.0 tag is not building the correct artifact. I personally do not have the access to create a tag in that repo afaik

- name: common-utils
repository: https://github.com/opensearch-project/common-utils.git
ref: 1.0
ref: d05a50e220a239f09a9048a368bc1b698cb7e6bd
Copy link
Member

Choose a reason for hiding this comment

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

What is this specific commit id? Why cant we use an existing tag?

Copy link
Member Author

Choose a reason for hiding this comment

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

The 1.0.0.0 tag is building an -rc artifact, not a release artifact

Signed-off-by: Marc Handalian <handalm@amazon.com>
@peternied peternied merged commit 18f07fa into opensearch-project:main Aug 25, 2021
alborotogarcia pushed a commit to alborotogarcia/opensearch-build that referenced this pull request Sep 7, 2021
Signed-off-by: Marc Handalian <handalm@amazon.com>
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.

4 participants