-
Notifications
You must be signed in to change notification settings - Fork 277
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
Release promotion pipeline enhancements #4750
Comments
Add on top of this list, we can also add things like:
to the central release workflow too. My concern is that we should have a resume function because the central promotion pipeline includes too many steps now. We do not want to switch back to manual trigger if one step failed in the process. Thanks. |
@peterzhuamazon IMO the workflows that you mentioned can be added into new central workflow for post release activities. |
Yeah that would also be good so we can separate these two. Thanks. |
Is your feature request related to a problem? Please describe
With #4748 closed, we were able to bring down the pipeline runtime from 1 hour 6min (1.3.16 release run) to 21min (1.3.17 release run) which is around 68%. However, there are still few other jobs that are manually triggered today.
Listing them here:
Other enhancements that are out of the scope of this issue are:
Describe the solution you'd like
Add above workflows to automated centralized pipeline bringing us closer to #3676
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: