On check-in of all changes, deploy cancels: "No changes detected in base directory. Returning early from build"

Netlify Site Name: blast-api

Build settings attached. Note, I am NOT using a netlify.toml file as it seemed to cause issues setting up the build and the UI config was fine.

Problem: On every check-in to master, which is configured to trigger builds in Netlify, a build is triggered as desired. Unfortunately, no matter how many, how large the changes, it always cancels!

The build log is as follows (example: https://app.netlify.com/sites/blast-api/deploys/5f91c4fc0729d600075bbcee):

10:44:29 AM: Build ready to start
10:44:30 AM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
10:44:30 AM: build-image tag: v3.4.1
10:44:30 AM: buildbot version: 0a44c930054be748eff0c581d346282fece89cc0
10:44:31 AM: Fetching cached dependencies
10:44:31 AM: Starting to download cache of 135.4MB
10:44:33 AM: Finished downloading cache in 2.201351282s
10:44:33 AM: Starting to extract cac
10:44:36 AM: Finished extracting cache in 3.598670794s
10:44:36 AM: Finished fetching cache in 5.903589307s
10:44:36 AM: Starting to prepare the repo for build
10:44:37 AM: Preparing Git Reference refs/heads/master
10:44:39 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘System Architecture/Blast API/public’ versus ‘public/’ in the Netlify UI
10:44:39 AM: No changes detected in base directory. Returning early from build.
10:44:39 AM: Failed during stage ‘checking build content for changes’: Canceled build due to no content change
10:44:39 AM: Finished processing build request in 8.787778378s

The workaround is to go into the Deploys screen and manually trigger a clean build via:

“Trigger Deploy -> Clear cache and deploy site”

This works exactly as expected - but is manual!

My attention would be drawn towards

Different publish path detected, going to use the one specified in the Netlify configuration file: ‘System Architecture/Blast API/public’ versus ‘public/’ in the Netlify UI

Is the repo public? If so could you link it here, please?

While not a fix a temporary command a netlify.toml file might tell the builder to never skip.
(I noted you removed yours but hopefully, this works temporarily)
[build]
ignore = “/bin/false”

Sorry, the repo isn’t public :frowning:

I was drawn towards that path as well, but can’t seem to sort out what to do about this. I tried NOT specifying public as my Publish Directory, but that broke the site - and it still cancelled the build, with a different error:

3:18:59 PM: Build ready to start
3:19:01 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
3:19:01 PM: build-image tag: v3.4.1
3:19:01 PM: buildbot version: 0a44c930054be748eff0c581d346282fece89cc0
3:19:01 PM: Fetching cached dependencies
3:19:01 PM: Starting to download cache of 135.4MB
3:19:02 PM: Finished downloading cache in 1.114629364s
3:19:02 PM: Starting to extract cache
3:19:05 PM: Finished extracting cache in 2.842498294s
3:19:05 PM: Finished fetching cache in 4.034084016s
3:19:05 PM: Starting to prepare the repo for build
3:19:06 PM: Preparing Git Reference refs/heads/master
3:19:07 PM: No changes detected in base directory. Returning early from build.
3:19:07 PM: Failed during stage ‘checking build content for changes’: Canceled build due to no content change
3:19:07 PM: Finished processing build request in 6.572327352s

Hey @ccoffman,
I’ve seen something a bit like this before, over here --> Issues with base build directory during deploys. Would you mind adding another slash to the end of the publish directory in the UI and see if that fixes things? If not, we’ll keep digging.

1 Like