Manual deploy now wants to build with Hugo or Zola

Support
,
1

My netlify site name is prooftoys.netlify.app. I have searched, looked at recent posts, and asked the chatbot, but I don’t see my issue anywhere.

I have used Netlify for years through the CLI, using manual deploys. (I build the site locally with Hugo first.) Today suddenly when I issue my deploy in the same way as always:

$ netlify deploy --site prooftoys.netlify.app --dir public

The response is:

? Multiple possible build commands found (Use arrow keys or type to search)
❯ [Hugo] ‘hugo’
[Zola] ‘zola build’

Netlify wants me to choose a build command, but I just want to manually deploy as usual.

$ netlify --version
netlify-cli/17.38.1 darwin-arm64 node-v22.4.0

I don’t know what has changed.
Why is netlify wanting to build now?
How do I get back to the usual manual deployment?

Thanks,
Cris

2

The netlify deploy command seems to be trying to automatically find a build command even when not building. In my case, renaming config.toml to hugo.toml has worked around this issue.

3

You could just change the build command to “echo ‘No build command…’” in your netlify.toml

I’m assuming you are running a Hugo build prior to the manual deploy. If you have your netlify.toml setup correctly, you only have to run the following.

netlify deploy --prod

For turning off automatic builds (info)

If you don’t want to build automatic, you should check that automatic builds are turned off.

4

I just tried this and running netlify deploy doesn’t trigger a build in my project. Can you share a minimal reproduction?

5

Thanks for responding to this issue.

It is pretty clearly a bug somewhere in the Netlify CLI. See bug #6841 [v17.36.2]: Running into "Multiple possible build commands found" with builds disabled · Issue #6841 · netlify/cli · GitHub. Netlify has never done builds for me, and I have never requested them, but now it wants to know which build to do. I chose “hugo” once and let it proceed, and it did not appear to build.

I did find a workaround. See my comments on the bug report.