Deploy succeed but not actually reflected to the real site. "0 new files to upload"

I git pushed and auto-build was completed but the commits are not actually applied to the page.
Deploy summary says : All files already uploaded
All files already uploaded by a previous deploy with the same commits.

and the log says : 0 new files to upload , 0 new functions to upload
11:10:50 PM: Site is live
11:11:07 PM: Finished processing build request in 1m18.274106286s

I surely committed new lines to github master branch and the deploy details says it has succeed to publish the new commits. What can I do to make it actually reflected? Do i have to commit the new bundle.js?? I thought it is made automatically while building .

full log is like below

11:09:48 PM: Build ready to start

11:09:49 PM: build-image version: 9cade8af58c2cf3a17a1e9433d2e979149488837

11:09:49 PM: build-image tag: v3.3.5

11:09:49 PM: buildbot version: 2fd8f04962d5dbc77b79b9c2f5ab7a077e87376b

11:09:49 PM: Fetching cached dependencies

11:09:49 PM: Starting to download cache of 116.1MB

11:09:50 PM: Finished downloading cache in 891.950887ms

11:09:50 PM: Starting to extract cache

11:09:55 PM: Finished extracting cache in 5.294252045s

11:09:56 PM: Finished fetching cache in 6.28681259s

11:09:56 PM: Starting to prepare the repo for build

11:09:56 PM: Preparing Git Reference refs/heads/master

11:09:57 PM: Starting build script

11:09:57 PM: Installing dependencies

11:09:57 PM: Started restoring cached node version

11:10:00 PM: Finished restoring cached node version

11:10:01 PM: v10.19.0 is already installed.

11:10:02 PM: Now using node v10.19.0 (npm v6.13.4)

11:10:03 PM: Attempting ruby version 2.6.2, read from environment

11:10:04 PM: Using ruby version 2.6.2

11:10:05 PM: Using PHP version 5.6

11:10:05 PM: Started restoring cached node modules

11:10:05 PM: Finished restoring cached node modules

11:10:05 PM: Started restoring cached yarn cache

11:10:05 PM: Finished restoring cached yarn cache

11:10:06 PM: Installing NPM modules using Yarn version 1.17.0

11:10:06 PM: yarn install v1.17.0

11:10:07 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

11:10:07 PM: [1/4] Resolving packages...

11:10:08 PM: [2/4] Fetching packages...

11:10:27 PM: info fsevents@1.2.11: The platform "linux" is incompatible with this module.

11:10:27 PM: info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.

11:10:27 PM: [3/4] Linking dependencies...

11:10:27 PM: warning " > styled-components@5.0.0" has unmet peer dependency "react-is@>= 16.8.0".

11:10:32 PM: [4/4] Building fresh packages...

11:10:34 PM: success Saved lockfile.

11:10:34 PM: Done in 27.38s.

11:10:34 PM: NPM modules installed using Yarn

11:10:34 PM: Started restoring cached go cache

11:10:34 PM: Finished restoring cached go cache

11:10:34 PM: unset GOOS;

11:10:34 PM: unset GOARCH;

11:10:34 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';

11:10:34 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";

11:10:34 PM: go version >&2;

11:10:34 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';

11:10:34 PM: go version go1.12 linux/amd64

11:10:34 PM: Installing missing commands

11:10:34 PM: Verify run directory

11:10:34 PM: Executing user command: npx webpack

11:10:48 PM: npx: installed 322 in 13.921s

11:10:48 PM: One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:

11:10:48 PM: - webpack-cli (https://github.com/webpack/webpack-cli)

11:10:48 PM: The original webpack full-featured CLI.

11:10:48 PM: We will use "yarn" to install the CLI via "yarn add -D".

11:10:48 PM: Do you want to install 'webpack-cli' (yes/no):

11:10:49 PM: Skipping functions preparation step: no functions directory set

11:10:49 PM: Caching artifacts

11:10:49 PM: Started saving node modules

11:10:49 PM: Finished saving node modules

11:10:49 PM: Started saving yarn cache

11:10:49 PM: Finished saving yarn cache

11:10:49 PM: Started saving pip cache

11:10:49 PM: Finished saving pip cache

11:10:49 PM: Started saving emacs cask dependencies

11:10:49 PM: Finished saving emacs cask dependencies

11:10:49 PM: Started saving maven dependencies

11:10:49 PM: Finished saving maven dependencies

11:10:49 PM: Started saving boot dependencies

11:10:49 PM: Finished saving boot dependencies

11:10:49 PM: Started saving go dependencies

11:10:49 PM: Finished saving go dependencies

11:10:49 PM: Build script success

11:10:49 PM: Starting to deploy site from 'dist/'

11:10:49 PM: Creating deploy tree

11:10:49 PM: 0 new files to upload

11:10:49 PM: Starting post processing

11:10:49 PM: 0 new functions to upload

11:10:50 PM: Post processing done

11:10:50 PM: Site is live

11:11:07 PM: Finished processing build request in 1m18.274106286s

What file(s) did you change? Or can you share a link to the commit in question?

1 Like

Hi, @lolsm, it would seem that the new build generates files which are identical to some previous build.

Can you confirm that the build generates changes locally? Also, would you please send us a link to the deploy logs posted?

You can private message (PM) that to one of our support staff and I’ve confirmed that PMs are enabled for your community login. Note, that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.

Hi, @lolsm. I received the PM reply from you.

Would you please see if this issue is being caused by the build cache at Netlify. To test this, please try triggering a new build of the same deploy you linked me to but clearing the build cache when doing so. This can be done with the button and sub-option shown in this screenshot:

Would you us know if that option causes the file changes to appear in the deployed site?

no. i tried that several times, but it didn’t make any differences.

What files are changing in the local build which are not changing at Netlify? Also, how are the files being changed between builds? What is different about them?