Skip to content

CI is pretty inefficient building, testing containers #234

Description

@brews

CI is inefficient at building, testing containers. I'm thinking beyond #207. We build containers for testing and then again to push to edge or a new release. It's not just that this takes up time and resources but dodola builds are non-deterministic (because we're not using conda-lock, see #197). We could have a container pass CI tests and then get (re)built and pushed for a release in an untested broken package.

It would be nice to sit and fix but I wonder if it's worth the added trouble and complexity given that this is such a small and purpose-built application.

Activity

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

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