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 additional workflows to central promotion workflows #4753

Merged
merged 5 commits into from
Jun 11, 2024

Conversation

gaiksaya
Copy link
Member

@gaiksaya gaiksaya commented Jun 10, 2024

Description

This changed adds below workflows to central promotion workflow.

  • Docker promotion
  • Maven promotion
  • Cloudfront invalidation
  • Validation workflow.

Also replaces the old jenkinsFile and test cases with new one.

The flow would look like below
image

Issues Resolved

closes #4750

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.

@gaiksaya gaiksaya changed the title Add cloudfront invalidation, validation and docker promotion workflows Add additional workflows to central promotion workflows Jun 10, 2024
Signed-off-by: Sayali Gaikawad <[email protected]>
steps {
script {
echo 'Invalidating cloudfront'
def version=params.RELEASE_VERSION.find(/\d/)
Copy link
Member

Choose a reason for hiding this comment

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

Can you change this to name major_version, or it will be pretty confusing.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done!

}
steps {
echo 'Triggering publish to maven workflow'
build job: 'publish-to-maven', wait: true, parameters: [
Copy link
Member Author

Choose a reason for hiding this comment

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

@peterzhuamazon @prudhvigodithi Do we want to wait for maven? IMO let's not?

Copy link
Member

Choose a reason for hiding this comment

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

I think if the previous validation failed, then wait or error out the run.
Else, I have no concerns on straight follow up with maven release.

Copy link
Member Author

Choose a reason for hiding this comment

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

It will error out. Tested that. The motivation to set wait:false is because maven takes a lot of time. And we do not want to wait in the release call for that. Let me know if that is okay.

Thanks!

gaiksaya added 3 commits June 10, 2024 13:49
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
Copy link

codecov bot commented Jun 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.29%. Comparing base (8816c60) to head (bfa5d00).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4753      +/-   ##
==========================================
+ Coverage   92.04%   92.29%   +0.24%     
==========================================
  Files         193      193              
  Lines        6411     6411              
==========================================
+ Hits         5901     5917      +16     
+ Misses        510      494      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gaiksaya gaiksaya merged commit 009e2bb into opensearch-project:main Jun 11, 2024
12 checks passed
@gaiksaya gaiksaya deleted the add-workflows branch June 11, 2024 21:32
@gaiksaya gaiksaya mentioned this pull request Jun 11, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

Release promotion pipeline enhancements
2 participants