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.

Sign up for GitHub

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

Jump to bottom

Document what's going on in terms of caching #36

Open
djc opened this issue Jul 20, 2019 · 3 comments
Open

Document what's going on in terms of caching #36

djc opened this issue Jul 20, 2019 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@djc
Copy link
Contributor

djc commented Jul 20, 2019

Just trying this out on Quinn right now, it looks very helpful. It would be neat if documentation (the README) what, if anything, was going on in terms of caching.
@epage
Copy link
Contributor

epage commented Jul 21, 2019

Good point that we should document this for people unfamiliar with Azure Pipelines. As of right now, it doesn't support any caching, so neither do the templates we provide.

@epage epage added the documentation Improvements or additions to documentation label Jul 21, 2019
@jonhoo
Copy link
Collaborator

jonhoo commented Jul 21, 2019

Azure has only recently gotten support for caching, and it is slowly rolling out. As @epage says, the CI scripts here do not currently support caching at all :) The discussion to follow on the Azure side is microsoft/azure-pipelines-yaml#113.

@djc
Copy link
Contributor Author

djc commented Jul 21, 2019

Maybe this should then be reformulated as "Add support for caching"? I recently used it with Bitbucket pipelines and found the decreased turnaround time quite attractive.

@jonhoo jonhoo mentioned this issue Jan 20, 2020
Open
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@epage @djc @jonhoo