Skip to content

Flatten CI workflow & remove unnecessary CI caching #36

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

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

stig
Copy link
Contributor

@stig stig commented Mar 22, 2024

The CI cache is tied to as single branch, and is not very effective. It is my estimation that we don't build this often enough that the caching is worth the extra complexity in the config.

Flatten the workflow so the tests don't have to depend on the check. This means fewer CI roundtrips to find out that both check and test jobs fail.

@stig stig requested a review from a team as a code owner March 22, 2024 13:08
@stig stig force-pushed the remove-useless-caching branch from 36d8408 to d31736e Compare March 22, 2024 13:09
@stig stig force-pushed the remove-useless-caching branch from d31736e to 07e597c Compare March 22, 2024 13:13
The CI cache is tied to as single branch, and is not very effective.
It is my estimation that we don't build this often enough that the
caching is worth the extra complexity in the config.

Flatten the workflow so the tests don't have to depend on the check.
This means fewer CI roundtrips to find out that both check and test
jobs fail.
Copy link
Contributor

@calvis calvis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like lein deps takes 2s so this seems fine to me

@stig stig merged commit 83e8feb into master Mar 22, 2024
@stig stig deleted the remove-useless-caching branch March 22, 2024 13:30
- run: lein deps

- run: lein check
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about running lein check in the test job? Save a container.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that seems sensible. I had already merged, so made a new PR: #38

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

Successfully merging this pull request may close these issues.

4 participants