Skip to content
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

Identify and resolve CircleCI cache key conflicts #66

Open
jrgriffiniii opened this issue Jun 15, 2022 · 1 comment
Open

Identify and resolve CircleCI cache key conflicts #66

jrgriffiniii opened this issue Jun 15, 2022 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jrgriffiniii
Copy link
Contributor

As discovered within https://github.com/samvera/browse-everything/pull/403/files#r898011114, there seem to be cases where the Ruby and Rails versions are used to generate CircleCI cache keys which cannot readily be reused without introducing breaking changes for a given branch.

@jrgriffiniii jrgriffiniii self-assigned this Jun 15, 2022
@jrgriffiniii jrgriffiniii added the bug Something isn't working label Jun 15, 2022
@jrgriffiniii jrgriffiniii added this to the 1.0.3 milestone Jun 15, 2022
@cjcolvar
Copy link
Member

When looking into this yesterday I had the thought of dropping the bundle command in favor of the official ruby orb's command, but it looks like it might have the same sort of problem. It might still be worth considering using it anyways to avoid having to maintain the command ourselves.
https://github.com/CircleCI-Public/ruby-orb/blob/365d475512a3b4eafca54ece98a878f93aa49b30/src/commands/install-deps.yml#L36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants