Skip to content

ci: improve speeds #3031

Closed
Closed

Description

@ammario

Problem

Basic changes like #3030 wait 20m before they're merged. The culprit is hefty postgres and windows integration tests.

These tests are probably difficult to speed up. P

The most notable caveat to path based filtering is the action may use scripts and files outside of the main language. For example, a go test action may use a test.sh script and a Makefile. If we decide to use path filtering, we should do so sparingly, as there's an inescapable trade off between speed and correctness.

Definition of done

improve CI speeds from (20m?) to (?). One suggested path: we could use path based filtering or different triggers (cron or master only) to speed up the average Pull Request?

Activity

  1. spikecurtis commented on Jul 18, 2022

    @spikecurtis
    Collaborator

    One way to improve speed: #2476

  2. misskniss commented on Jul 26, 2022

    @misskniss

    @ammario - you merged some PRs over the weekend for CI - are those meant to fix this?
    How fast is fast?

  3. ammario commented on Jul 26, 2022

    @ammario
    MemberAuthor

    @misskniss yes they were. I'll go ahead and close this out. I expect my changes to cut the average wait time in half.

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