12:25:36 AM: Build ready to start
12:25:38 AM: build-image version: d2c6dbeac570350a387d832f64bc980dc964ad65 (focal)
12:25:38 AM: build-image tag: v4.8.0
12:25:38 AM: buildbot version: 4aaa27647e859c2d38cfbb25901ceae1e7f3eeae
12:25:38 AM: Fetching cached dependencies
12:25:46 AM: Finished downloading cache in 8.022868523s
12:25:46 AM: Starting to extract cache
12:26:31 AM: Finished extracting cache in 45.081511699s
12:26:31 AM: Finished fetching cache in 53.200071562s
12:26:31 AM: Starting to prepare the repo for build
12:26:32 AM: Preparing Git Reference pull/43/head
12:26:33 AM: Parsing package.json dependencies
12:26:34 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘packages/core-player/build’ versus ‘’ in the Netlify UI
12:26:34 AM: Different functions path detected, going to use the one specified in the Netlify configuration file: ‘packages/core-player/src/api’ versus ‘’ in the Netlify UI
12:26:34 AM: Different build command detected, going to use the one specified in the Netlify configuration file: ‘yarn build’ versus ‘’ in the Netlify UI
12:26:34 AM: No changes detected in base directory. Returning early from build.
12:26:34 AM: Creating deploy upload records
12:26:34 AM: Failed during stage ‘checking build content for changes’: Canceled build due to no content change
12:26:34 AM: Finished processing build request in 56.224293426s
I’m not sure that’s the case, I don’t see any of my build steps in the build log.
Meaning, even if I altered my build script to create a random file, it doesn’t seem like it would make a difference if the build script isn’t even running. Netlify is perhaps hashing a certain folder in the repo to scan for content changes ?
The problem is we have external assets that are copied into the repo at build time…
So if I needed to create a new file to force a re-build, I would have to then do it during the pre-commit hook… and frankly, since they are changes that don’t affect our production site, I would indeed prefer to NOT use build minutes/instances and deal with this as a notifications problem (which is what I think we agree this is) instead of a build problem
I’d based that assumption on the fact that it says it was running for 56.22s, which isn’t an immediate failure.
If that’s the case, are you sure that the system you’re using isn’t throwing an error when it determines that the input data hasn’t changed?
I’m just not sure how Netlify could be making the determination that the build hasn’t changed from only input data, and I’ve certainly never experienced anything like that, even when clients trigger webhook based builds of exactly the same content multiple times in a row.
We rarely do this, so don’t encounter it very often, but at some point historically we adapted to making inconsequential changes to non-display files, like adding/removing a space from the end of a line when we want a commit with no actual source changes to trigger a build.
We aren’t bitten by it day to day because most builds are triggered via webhook which seems to circumvent the “unchanged source” handling.