Skip to content

consider consolidating health check builds #307

Open

Description

@devoncarew

The health check workflow runs several (~6) builds per PR; we may want to consider consolidating the checks into one build, just for a simpler presentation in the PR UI. Here's the existing PR checks UI:

Screenshot 2024-10-15 at 10 29 57 AM

cc @mosuem

Activity

  1. mosuem commented on Oct 16, 2024

    @mosuem
    Member

    We split them up a while ago, to make it easier to understand which one failed. I am fine with switching back though.

  2. devoncarew commented on Oct 16, 2024

    @devoncarew
    ContributorAuthor

    Perhaps we could run them as separate steps in a build? Or have some other way to group the output to help call out which steps failed.

  3. mosuem commented on Oct 17, 2024

    @mosuem
    Member

    I normally only look at the steps which failed, which is why am fine with the current solution. I don't think there is a way to group actions, that would be ideal..

    What do you mean with run them as separate steps in a build?

  4. devoncarew commented on Oct 17, 2024

    @devoncarew
    ContributorAuthor

    Something like:

    Screenshot 2024-10-17 at 9 13 56 AM

    I'd have to look at how the health.yml file is set up - it might surface as having individual steps in a steps: section? It would probably mean a bit of an architectural change to the file.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions