Thanks to visit codestin.com
Credit goes to github.com

Skip to content

ci: improve speeds #3031

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #3042 ...
ammario opened this issue Jul 18, 2022 · 3 comments
Closed
Tracked by #3042 ...

ci: improve speeds #3031

ammario opened this issue Jul 18, 2022 · 3 comments

Comments

@ammario
Copy link
Member

ammario commented Jul 18, 2022

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?

@spikecurtis
Copy link
Contributor

One way to improve speed: #2476

@misskniss
Copy link

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

@ammario
Copy link
Member Author

ammario commented Jul 26, 2022

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants