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

Document how to use this in typical CI runners #1

Closed
mattip opened this issue Mar 22, 2020 · 4 comments
Closed

Document how to use this in typical CI runners #1

mattip opened this issue Mar 22, 2020 · 4 comments
Assignees

Comments

@mattip
Copy link

mattip commented Mar 22, 2020

This is great! Could you open a space in the README or other documentation to demonstrate using this in Ci runners like travis, azure pipelines, or github actions which are used in many open source projects? The CI runner documentation about best practices with caching is not always clear: when a cache actually saves CI bandwidth and when it doesn't.

@EpicWink EpicWink self-assigned this Mar 27, 2020
@EpicWink
Copy link
Owner

Sure, I'll get on it. An issue is running a persistent program on these runners: as far as I know, only BYO runners (where the user has full control over the server) can run these programs effectively

@mattip
Copy link
Author

mattip commented Mar 27, 2020

ahh, so this won't work with travis :( ?

@EpicWink
Copy link
Owner

EpicWink commented Mar 27, 2020

Not unless you can use your own runners on Travis (which you can with Enterprise Travis). In any case, Travis already supplies a different form of caching for pip: see their documentation

@mattip
Copy link
Author

mattip commented Mar 27, 2020

OK, feel free to close this then.

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

No branches or pull requests

2 participants