We’re using your example 6 with our monorepo:
base = 'nuxt-app'
command = 'CI= yarn generate'
publish = 'dist'
ignore = 'git diff --quiet $COMMIT_REF $CACHED_COMMIT_REF -- ../library ./ ../yarn.lock'
This works fine except it means that when someone uses “Deploy site” from the dashboard, it usually always gets Cancelled.
Is there anyway we can support “Deploy site” from the dashboard and trigger deploys of changes in our repo that occur outside of the base directory of our monorepo project?
Unfortunately, there’s no way to do that. You will have to force the builds using
exit 1 as the ignore script or always build by clearing the cache.
I don’t think “Clear cache and deploy site” works for this use case either. I just tried it and got the following result:
10:21:23 AM: Build ready to start
10:21:29 AM: build-image version: d2c6dbeac570350a387d832f64bc980dc964ad65 (focal)
10:21:29 AM: build-image tag: v4.8.0
10:21:29 AM: buildbot version: e58b6be665675c0f99b33132a8c1eec1f775eba1
10:21:29 AM: Building without cache
10:21:29 AM: Starting to prepare the repo for build
10:21:30 AM: No cached dependencies found. Cloning fresh repo
10:21:30 AM: git clone firstname.lastname@example.org:xxxx/xxxxx
10:21:39 AM: Preparing Git Reference refs/heads/main
10:21:40 AM: Parsing package.json dependencies
10:21:41 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'nuxt-app/dist' versus 'dist' in the Netlify UI
10:21:41 AM: Detected ignore command in Netlify configuration file. Proceeding with the specified command: 'git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF ../library ./ ../yarn.lock'
10:21:41 AM: User-specified ignore command returned exit code 0. Returning early from build.
10:21:41 AM: Creating deploy upload records
10:21:41 AM: Failed during stage 'checking build content for changes': Canceled build due to no content change
10:21:42 AM: Finished processing build request in 12.548533113s
Is there something I’m doing wrong here? If not, it’d love a 3rd deploy option that was like “Force deploy” or something like that.
Hey there, @weotch
Thanks so much for your patience here-- the Support team has been underwater this past week and we are responding slower than we would like to some questions.
Are you still encountering obstacles here? If you are, can you please share the specific site in question? I’ll stay tuned for a response from you.
We have workarounds for this. This is more of a nice-to-have feature request than a bug report.
We have opened up a feature request for this to be considered by our product team in the future. Thank you for your feedback!