Figure out caching on Azure CI about cypress-example-kitchensink HOT 7 CLOSED

Azure DevOps Pipeline caching came out of preview the other day. It would be great to have an example of how to cache the Cypress binary in YAML Pipelines, as I am currently struggling to make it work.

from cypress-example-kitchensink.

More details suggested by other MVPs

• https://stackoverflow.com/questions/44546183/correct-way-to-use-npm-cache-vs-team-services
• https://visualstudio.uservoice.com/forums/330519-azure-devops-formerly-visual-studio-team-services/suggestions/32044321-improve-hosted-build-agent-performance-with-build

Seems Azure CI team is working on general caching solution, might make sense to wait for them

from cypress-example-kitchensink.

I know I am late to the party, but a small improvement on @ekulabuhov post:
Instead of hard coding the path you can also use path: $(LOCALAPPDATA)/Cypress, also see this

from cypress-example-kitchensink.

• resources at https://docs.microsoft.com/en-us/azure/devops/artifacts/npm/npmrc?view=vsts&tabs=new-nav do not show how to cache node modules

from cypress-example-kitchensink.

Sample project: https://github.com/MicrosoftDocs/pipelines-javascript but does not show any caching for node_modules or ~/.npm folders

from cypress-example-kitchensink.

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from cypress-example-kitchensink.

Hi! It might be useful to add that on a windows based image the path is different and looks like this:

- task: CacheBeta@1
  inputs:
    key: 'cypress | $(Agent.OS) | package-lock.json'
    path: 'C:\Users\VssAdministrator\AppData\Local\Cypress'
    restoreKeys: 'cypress | $(Agent.OS) | package-lock.json'
  displayName: Cache cypress binary

Unfortunately, caching in Azure Pipelines is a bit crippled due to security restrictions described here: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops#cache-isolation-and-security

Basically, caches are isolated between different branches which makes them less useful when used with short lived feature branches.

from cypress-example-kitchensink.