You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
We need to create an automated mechanism to migrate the artifacts generated in staging environment to production environment
Describe the solution you'd like
All the staging artifacts generated should be migrated to production automatically. This includes daily build artifacts, distribution artifacts, native plugin/ plugin zips, docker artifacts.
bbarani
changed the title
Automated mechanism to migrate artifacts from staging to production environment
[Meta]Automated mechanism to migrate artifacts from staging to production environment
Nov 29, 2021
dblock
changed the title
[Meta]Automated mechanism to migrate artifacts from staging to production environment
Automate pushing staging artifacts to production environment
Jan 11, 2022
dblock
changed the title
Automate pushing staging artifacts to production environment
Automate pushing staging artifacts to production during releases
Jan 11, 2022
dblock
changed the title
Automate pushing staging artifacts to production during releases
Automate pushing staging artifacts to production during release
Jan 11, 2022
I would say yes however, This includes daily build artifacts are not pushed today but are accessible via ci.opensearch.org
I don't think we need to push those to production. The issue title says during release which we have in place today.
Thanks!
Is your feature request related to a problem? Please describe
We need to create an automated mechanism to migrate the artifacts generated in staging environment to production environment
Describe the solution you'd like
All the staging artifacts generated should be migrated to production automatically. This includes daily build artifacts, distribution artifacts, native plugin/ plugin zips, docker artifacts.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: