script: # Modify the commands below to build your repository.
- npm install -g firebase-tools
- npm install
- npm run build
- firebase deploy --token=$FIREBASE_TOKEN --project ***** --non-interactive
firebase-tools is not cached, but it is in "globalnode".
am I doing this wrong?
Hi @Johan Blomgren,
the 'node' cache is one of the pre configured caches that we have set up. If you want to have additional caches like globalnode or usernode, you have to configure the paths there to those caches.
More information is here in the 'Custom caches for other build tools and directories': https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html
Sorry I missed that part.
Currently environment variables in the directory paths are not supported so $HOME in the usernode path should be replaced with the actual file path.
Can you check whether anything is cached inside the 'globalnode' cache (i.e. is just 'firebase-tools' not cached) ?
If that would be the case, maybe there is an issue with symlinks (e.g. the firebase-tools directory could be a symlink in which case it might not be cached).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs