qoQovery
GitHubconsoleWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceededchore/QOV-2108/remove-legacy-s3-deploy
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    chore(ci): remove legacy S3 deploy after CloudFront cutover (QOV-2108) The CloudFront origin buckets now serve console.qovery.com and console-staging.qovery.com, so the dual-target scaffolding from the migration is no longer needed: - drop the legacy bucket copy steps and the s3-bucket-name-with-cloudfront indirection; the origin bucket is now plain s3-bucket-name - make the CloudFront steps unconditional since both deploy flows set the bucket and distribution - remove the cloudflare-zone/cloudflare-token secrets, declared and passed but unused by any step
    nx run console:build --parallel=3 --configuration=development
Succeeded
read-write access token used
065cdb9a2846
50%

Cache hits

1 of 2 tasks used cache.

Protect cache integrity with sandboxing

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools