Skip to content
This repository was archived by the owner on Feb 16, 2025. It is now read-only.
This repository was archived by the owner on Feb 16, 2025. It is now read-only.

Rolling changes out to staging takes long due to canary  #727

@rogerthatdev

Description

@rogerthatdev

Problem

When making changes to website or api, staging changes to stage environment takes as long as it takes to roll out to prod due to the canary trigger. Could we reduce the time required for rolling out to staging by skipping canary and reserving it only for prod rollouts?

Steps to Reproduce

Steps to reproduce the behavior:
From a standing instance of emblem

  1. Activate the web-new-build trigger
  2. Observe triggers in the Cloud Build history page
  3. Watch several web-canary-staging triggers show up.

Expected behavior

Since web-canary-staging functions exactly as web-canary-prod (only difference being the triggering action), there's no value in demonstrating canary trigger twice unless we intend to illustrate a difference based on environment. For demonstration purposes, I'd rather changes roll out to staging at 100% immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions