I’m trying to optimize build minutes some by adding some files to the

ignoreChanges

section in my

lerna.json

. I see a log that lerna is ignoring the paths specified but it appears SEED still deployed because some of the files are not in any packages. I’m probably not doing this correctly. How can I get lerna and SEED to not deploy all my services by making a slight change in say my repo’s

README.md

at the root of my repo?

Hey @Jacob Hayes, it’s something on our roadmap. You will be able to specify a folder, and Seed will only check for changes within it. For example, if the folder structure looks like this:

/
  README.md
  package.json
  src/
    lib/
    services/
      serviceA/
      serviceB/

If you specified

src

, changes to

README.md

and

package.json

will not trigger a build.

Yes if you recall I had documentation in a folder and source in another. I would like 2 seed builds: 1 for docs (deploy as website) and 1 for the actual services

@Frank Our directory structure is like this:

README.md
package.json
yarn.lock
documentation/
packages/
services/

As long as I could specify multiple directories (services and packages) that would be great. Since we switched to yarn/lerna our build minutes and overall build time has gone through the roof and is likely to cause us to go over our allotted build minutes because everything deploys if any service or our internal packages needs a dependency update because of the yarn.lock changes at the root if there’s any package update. I’m happy to provide more info about our setup or feedback in general around this feature let me know

@Danny @Jacob Hayes got it 👍