Question: Can we cache the installation folders
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 276
- Forks
- 37
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 12
Description
Hello,
I have been using setup-cpp and I saw that it takes some time to run on GitHub-hosted environments (Windows and Ubuntu). So, I was wondering if it is possible to cache the installation of the tools I am using (e.g. cmake, ninja, vcpkg, etc..).
Technically, if all the jobs ran under the same OS environment, I don't see a reason why we cannot install the tools once and use them on a matrix configuration multiple times. Now, of course, being new to this, I may be unaware of its possibilities and how to do it. So, I would appreciate any information.
Kind regards,
PS: Sorry to open an issue for a question.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing setup-cpp’s installation flow and the GitHub Actions matrix behavior on Windows and Ubuntu; done should mean establishing whether installed CMake, Ninja, vcpkg, and similar tools can be reused across jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100