Skip to content

Tag-triggered container workflows #154

Description

@l-monninger

Summary

The container workflows are beginning to flake under various activity levels. It may be nice to adopt the tagged workflows approach from movement to prevent unnecessary building.

Note

Flakiness is likely to persist here since we are using the movement-runner GHA runner to obtain more disk space, as opposed to the more dynamic and scalable BuildJet runners.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featureThis issue introduces new behaviorpriority:mediumThis issue should be worked on progressively but does not need consistent immediate attention

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions