Skip to content

Figure out if we can optimize our GitHub actions with caching #134

@roypat

Description

@roypat

In the past, our docker building GitHub actions used to benefit from some caching of action artifacts, which allowed the post-merge build of the docker container to be skipped in favor or just reusing the artifacts from the pre-merge build (at least I remember something like this happening). It seems like a few months ago this stopped, but it'd be nice to get this functionality back, if only to avoid docker-container-building turning into a whole-day activity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions