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

Fix circleci caching paths #513

Closed
dyladan opened this issue Nov 9, 2019 · 6 comments
Closed

Fix circleci caching paths #513

dyladan opened this issue Nov 9, 2019 · 6 comments
Assignees

Comments

@dyladan
Copy link
Member

dyladan commented Nov 9, 2019

Is your feature request related to a problem? Please describe.

Circle CI caching paths include a * glob. According to the docs, globbing is not allowed in the paths array.

Describe the solution you'd like

Each package node module directory should be manually added to the globs array.

Please assign to me. PR incoming.

@dyladan
Copy link
Member Author

dyladan commented Nov 11, 2019

While I'm working on this, should we remove yarn.lock files from the cache? I added them because there was a packages/*/yarn.lock line before, but it may be a good idea to remove them so that the ci builds always get the latest version of node modules permissible by the package.json

@vmarchaud
Copy link
Member

yarn.lock files are inside the .gitignore so we shouldn't have any of them inside the repo. However i would argue that would be better to use them since the CI might install different deps version than we have in local.

@dyladan
Copy link
Member Author

dyladan commented Nov 11, 2019

They are cached by the circle ci caching layer, so they are created and persisted between multiple test runs until the cache breaks (by changing a package.json file).

@vmarchaud
Copy link
Member

Oh got it, for me which should either use them at every step (so commit them inside the repo) or not using them at all

@dyladan
Copy link
Member Author

dyladan commented Nov 11, 2019

I would argue for not using them at all. We want to make sure we get the versions of dependencies that our end users will get. It is up to them to lock their dependencies.

@mayurkale22
Copy link
Member

@dyladan Can we close this one?

@dyladan dyladan closed this as completed Nov 19, 2019
pichlermarc pushed a commit to dynatrace-oss-contrib/opentelemetry-js that referenced this issue Dec 15, 2023
* chore: update core to 0.20.0

* chore: fix test

* chore: review comments and lint

* chore: get example versions from previous update

* chore: lint
martinkuba pushed a commit to martinkuba/opentelemetry-js that referenced this issue Mar 13, 2024
* chore: update core to 0.20.0

* chore: fix test

* chore: review comments and lint

* chore: get example versions from previous update

* chore: lint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants