in pipelines: cache global npm modules?

[Johan Blomgren]

image: node:6.9.4
pipelines: 
  default: 
    - step: 
      caches: 
        - node 
        - globalnode
        - usernode
      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
definitions: 
  caches: 
    globalnode: /usr/local/lib/node_modules
    usernode: $HOME/.npm

firebase-tools is not cached, but it is in "globalnode".

am I doing this wrong? 

[Jeroen De Raedt]

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 

[Johan Blomgren]

I did read the documentation, and the posted config is based on my findings.

Does not my config define a "globalnode" and a "usernode" -cache?

Is this not the way to configure the paths?

definitions: 
  caches: 
    globalnode: /usr/local/lib/node_modules
    usernode: $HOME/.npm

[Jeroen De Raedt]

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).