Skip to content

Conversation

nikole-dunixi
Copy link

This solves issue: #57

Solution

I've pinned the dependencies at a version that works today and sets the tested Rust version to one that is also current.

Extra Credit

I've also added docker buildkit into the mix so the cargo dependencies are shared across each of the test-cases and saves some testing time. I don't know if there is any CI/CD in place already, but if the Docker version running is current this should be non-breaking

@nikole-dunixi nikole-dunixi force-pushed the feature/docker-cargo-caching branch from 428efb8 to 9826d67 Compare August 18, 2022 17:36
@nikole-dunixi
Copy link
Author

I didn't realize that there was a requirement for commits to be signed. I've setup GPG and then rebased my branch to resign all the commits before force-pushing to update this PR.

@ryanatallah
Copy link

@ucarion would you mind reviewing this change? It seems that there are a few improvements which are blocked by test failures.

@nikole-dunixi nikole-dunixi force-pushed the feature/docker-cargo-caching branch 6 times, most recently from ab608d0 to f758762 Compare June 6, 2023 04:30
@nikole-dunixi nikole-dunixi force-pushed the feature/docker-cargo-caching branch from f758762 to cfb134a Compare June 6, 2023 04:33
@nikole-dunixi
Copy link
Author

@ucarion My apologies for any inconvenience, but I didn't realize when I revoked my older GPG key that it actually unverified my previous commits. I've re-signed them.

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.

2 participants