How to persist_to_workspace using a recursive pattern match

Build Environment
1

I want to persist_to_workspace some Relay.js build-files. These are generated automatically in a deeply nested directory structure. They have a common file extension (.graphql.js) and live in a commonly named directory (__generated__), so this should be pretty straightforward.

However it seems that the Go glob pattern-matching algorithm that is used does not support recursive lookup - see here.

This feels like a massive limitation. Is there any way around doing something horrible like this:

- persist_to_workspace:
      root: ~/repo
      paths:
         - '*/__generated__/*'
         - '*/*/__generated__/*'
        - '*/*/*/__generated__/*'
        - '*/*/*/*/__generated__/*'
        - '*/*/*/*/*/__generated__/*'
        - '*/*/*/*/*/*/__generated__/*'
3 Likes
2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.