qo
Qovery
GitHub
console
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
console
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
staging
67434a14 feat(ci): deploy production to CloudFront origin bucket (QOV-2108) (#2841)
by Dubroeucqg
D
Succeeded
staging
67434a14 feat(ci): deploy production to CloudFront origin bucket (QOV-2108) (#2841)
by Dubroeucqg
D
Succeeded
staging
a3634318 feat(ci): deploy staging to CloudFront origin bucket (QOV-2108) (#2839) Dual-target deploy during the CloudFront migration: staging builds now also publish to qovery-console-staging (the OAC origin behind CloudFront) and invalidate the cached index.html. The legacy bucket keeps serving console-staging.qovery.com until the DNS cutover. Production is intentionally unchanged; it opts in later by passing s3-bucket-name-with-cloudfront and cloudfront-distribution-id. Requires the frontend-code-push IAM policy update (s3:PutObject on the new bucket + cloudfront:CreateInvalidation) before merge.
by Dubroeucqg
D
Previous page
Previous
Next
Next page