"No build command found, continuing to publishing" Build stuck at building phase

yaya, which site do you have a problem with? thanks.

hi all, i am gathering threads here from the various folks who have been experiencing this issue. We are aware of the problem and are investigating, I’ll get you more more updates as we know more. Stay tuned - and thank you for your patience as we look into this.

-Perry

2 Likes

@perry Thanks for the reply. Info attached/below:

Site name: advertorial-immediate
Live URL: https://advertorial.immediate.co.uk/
Most recent deploy log: Netlify App
Successful deploy log example: Netlify App
Build settings screenshot:


Package.json: { "name": "new-feature", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "author": "", "license": "ISC", "devDependencies": { "browser-sync": "^2.26.7", "gulp": "^3.9.1", "gulp-autoprefixer": "^5.0.0", "gulp-cssnano": "^2.1.3", "gulp-inject-string": "^1.1.1", "gulp-plumber": "^1.2.0", "gulp-sass": "^4.0.1", "gulp-tinypng": "^1.0.2", "run-sequence": "^2.2.1" } }

@Imagine, @Yaya, @bennettfeely and everyone else - can you please retry your deploys? we believe we have fixed the problem. let us know what happens please!

2 Likes

Just deployed successfully. Thanks!

@perry Yep now building successfully. Thank you for resolving/letting us know

1 Like

Deploys successfully now. Thank you!

1 Like

@perry Thank you for fixing this. Really appreciate the help!

1 Like

@perry Successful deployment! Thank you for your responsiveness!

1 Like

@perry Problem resolved. Thank you.

1 Like

@perry – this is happening to me. It just started this morning (everything was working fine 36 hours ago Monday evening the 13th) – although note that I haven’t pushed anything to my repo in 36 hours.

Site name: rbhi
Live URL: https://rbhi.netlify.app
Most recent deploy log: Netlify App
Successful deploy log example: Netlify App

Interesting – I uninstalled the Algolia Build Plugin that I had installed this morning and re-ran deploy #5f884508bde96c007ea6b4b and it went just fine:

thanks for letting us know, @rprob. Seems likely this is an issue with the algolia plugin, which Netlify doesn’t manage directly (or provide direct support for) luckily, they have a whole support operation.

See my guidance at the end of this thread:

https://answers.netlify.com/t/algolia-search-plugin-with-custom-domain-name-domain-not-allowed/23931/2

on how to report a problem and how to get help from them!