Problem using Appveyor build cache
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Even when packages and paket-files are successfully restored from cache, paket restore is restoring (or at least downloading) all packages again. Problem reported here
The same happen if you test this manually with RDP to the AppVeyor build VM before paket restore is called. Subsequent call to paket restore does not trigger dependencies download.
Probably something else should be cached, cannot figure out what. Or maybe the fact that every new build is happening in new VM affects something...
Repro steps
It can be reproduced by forking the repository from original post and creating AppVeyor build against it.
Expected behavior
Dependencies should not be downloaded again
Actual behavior
Dependencies which are already restored from cache are being downloaded.
Known workarounds
Not aware of
Contributor guide
No contributing guide indexed for this repository
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
Start with the AppVeyor build configuration and the paket restore step, comparing the cached packages and paket-files with the manual RDP reproduction. Check what paket restore treats as already restored and whether a new build VM changes that state. Done means a forked AppVeyor build reuses cached dependencies without downloading them again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100