ymedlop/npm-cache-resource

project-path working?

Closed this issue · 3 comments

I'm trying to use the 'project-path' setting and it seems to ignore it and the checking never triggers. Here's the excerpt from my YAML file.

  • name: npm-repo-cache
    type: npm-cache # as defined above
    source:
    <<: *repo-source # the source is the same as the corresponding git resource ...
    paths: # ... except that it's only interested in files listing dependencies
    - package.json
    project-path: project-ui # this is where my package.json lives

Hi,

I going to do a example to see what happens

@ymedlop Any update on this? Seems like paths: is still not working. This is a neat tool to add to my pipeline! :)

Hi,

I updated the Example. I did the example and everything is working!.

If we check the git resource doc.

paths: Optional. If specified (as a list of glob patterns), only changes to the specified files will yield new versions from check.

I believe the problem was here. You have to indicate the right path of the package.json.

   # a resource caching the dependencies listed in the source repository
  - name: npm-repo-cache
    type: npm-cache # as defined above
    source:
      <<: *repo-source # the source is the same as the corresponding git resource ...
      paths: # ... except that it's only interested in files listing dependencies
        - app/package.json # only trigger when package.json is changed
      project-path: app # path where it is our package.json