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

If a project B use project A as a junction, B should not try to use the bst remote cache of A (at least by default) #1839

Open
nanonyme opened this issue Apr 29, 2023 · 1 comment · May be fixed by #1941

Comments

@nanonyme
Copy link
Contributor

nanonyme commented Apr 29, 2023

Opening a new issue, this has regressed #401

Same reason as before. If project A is popular, this will literally kill the cache server.

@nanonyme
Copy link
Contributor Author

Though seems current behaviour is potentially worse than how it was back with original issue. Current behaviour is project B cache is never considered for project A artifacts meaning when the artifacts go out of cache for project A, they will never be considered cached.

abderrahim added a commit that referenced this issue Aug 2, 2024
This makes a junction use the artifact cache of the parent project
before the ones defined for the junction

This was originally done in 24c0de1,
but regressed at some point

Fixes #1839
abderrahim added a commit that referenced this issue Aug 2, 2024
This makes a junction use the artifact cache of the parent project
before the ones defined for the junction

This was originally done in 24c0de1,
but regressed at some point

Fixes #1839
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 a pull request may close this issue.

1 participant