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

[Bug]: Add workflows to verify all expected maven artifacts are published for a release #3463

Closed
saratvemulapalli opened this issue May 3, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@saratvemulapalli
Copy link
Member

saratvemulapalli commented May 3, 2023

Describe the bug

Coming from: opensearch-project/job-scheduler#374
Few maven publish workflows within a component changed and published artifacts in a different location.
This caused problems.

We identified the problem by manually looking at maven co-ordinates and these should be written as automated workflows and a pre-check for gating the release.

Proposal

Lets add workflows to verify all expected maven co-ordinates have expected artifacts before we officially release OpenSearch distribution.
This should help us automate and verify this doesn't happen for any component within the distribution.

@saratvemulapalli saratvemulapalli added bug Something isn't working untriaged Issues that have not yet been triaged labels May 3, 2023
@saratvemulapalli saratvemulapalli changed the title [Bug]: Add workflows to verify all maven artifacts are published for a release [Bug]: Add workflows to verify all expected maven artifacts are published for a release May 3, 2023
@jordarlu jordarlu removed the untriaged Issues that have not yet been triaged label May 9, 2023
@jordarlu
Copy link
Contributor

jordarlu commented May 9, 2023

Issue is valid, we will need a brainstorming session to finalize the design before moving forward.

@gaiksaya
Copy link
Member

gaiksaya commented May 9, 2023

Related: #2928

@peterzhuamazon
Copy link
Member

I think this is duplicated with #2928 @saratvemulapalli is it ok we close this issue and sync the comment to the old one?

Thanks.

@saratvemulapalli
Copy link
Member Author

Thanks folks. Yup the issue #2928 captures it.

@saratvemulapalli
Copy link
Member Author

saratvemulapalli commented May 11, 2023

Duplicate of #2928

@saratvemulapalli saratvemulapalli closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2023
@saratvemulapalli saratvemulapalli marked this as a duplicate of #2928 May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants