Fresh Hugo deployment failed

Support
,
1

I need advice to debug deploy Netlify App
(console ouput appended below).

NB: This is a Hugo-generated site that i am starting over from scratch, since continuous deployment from Github stopped working. I did check docs & community posts, and - having found that many users w/ same problem fixed it by upgrading HUGO_VERSION in netlify.toml file to 0.60.1 - i did upgrade that setting (was previously on version 0.4x) in Netlify… But now i wonder if that is compatible with software i used to generate this site (i.e. : Blogdown package in RStudio).

Anyway: I have no clue as to why these templates should fail to render, so if anyone can throw me a clue, i’d be much obliged -thanks!

8<-----(snip)----->8

1:29:06 PM: Build ready to start
1:31:08 PM: build-image version: 8e315e54bc4032a32e73290be556cde4f8348c12
1:31:08 PM: build-image tag: v2.8.2
1:31:08 PM: buildbot version: 45cd00068410d70db72c9672cdd014995488e12a
1:31:08 PM: Fetching cached dependencies
1:31:08 PM: Starting to download cache of 254.9KB
1:31:08 PM: Finished downloading cache in 169.779364ms
1:31:08 PM: Starting to extract cache
1:31:09 PM: Failed to fetch cache, continuing with build
1:31:09 PM: Starting to prepare the repo for build
1:31:09 PM: No cached dependencies found. Cloning fresh repo
1:31:09 PM: git clone GitHub - ludwa6/rf_2: ReFarmer blog, v2
1:31:10 PM: Preparing Git Reference refs/heads/master
1:31:10 PM: Starting build script
1:31:10 PM: Installing dependencies
1:31:11 PM: Downloading and installing node v10.19.0…
1:31:12 PM: Downloading https://nodejs.org/dist/v10.19.0/node-v10.19.0-linux-x64.tar.xz…
1:31:12 PM:
################################
1:31:12 PM: 45.0%
1:31:12 PM:
#############################################
1:31:12 PM: ########################### 100.0%
1:31:12 PM: Computing checksum with sha256sum
1:31:12 PM: Checksums matched!
1:31:15 PM: Now using node v10.19.0 (npm v6.13.4)
1:31:15 PM: Attempting ruby version 2.6.2, read from environment
1:31:16 PM: Using ruby version 2.6.2
1:31:16 PM: Using PHP version 5.6
1:31:16 PM: Installing Hugo 0.60.1
1:31:18 PM: Hugo Static Site Generator v0.60.1-96066756 linux/amd64 BuildDate: 2019-11-29T14:57:23Z
1:31:18 PM: Started restoring cached go cache
1:31:18 PM: Finished restoring cached go cache
1:31:18 PM: unset GOOS;
1:31:18 PM: unset GOARCH;
1:31:18 PM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.12.linux.amd64’;
1:31:18 PM: export PATH=“/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}”;
1:31:18 PM: go version >&2;
1:31:18 PM: export GIMME_ENV=‘/opt/buildhome/.gimme/env/go1.12.linux.amd64.env’;
1:31:18 PM: go version go1.12 linux/amd64
1:31:18 PM: Installing missing commands
1:31:18 PM: Verify run directory
1:31:18 PM: Executing user command: hugo
1:31:18 PM: Building sites …
1:31:18 PM: ERROR 2020/02/21 13:31:18 render of “taxonomy” failed: “/opt/build/repo/themes/Mainroad/layouts/_default/baseof.html:18:55”: execute of template failed: template: _default/list.html:18:55: executing “_default/list.html” at <resources.ExecuteAsTemplate>: error calling ExecuteAsTemplate: type not supported in Resource transformations
1:31:18 PM: ERROR 2020/02/21 13:31:18 render of “taxonomy” failed: “/opt/build/repo/themes/Mainroad/layouts/_default/baseof.html:18:55”: execute of template failed: template: _default/list.html:18:55: executing “_default/list.html” at <resources.ExecuteAsTemplate>: error calling ExecuteAsTemplate: type not supported in Resource transformations
1:31:18 PM: ERROR 2020/02/21 13:31:18 render of “taxonomyTerm” failed: “/opt/build/repo/themes/Mainroad/layouts/_default/baseof.html:18:55”: execute of template failed: template: _default/list.html:18:55: executing “_default/list.html” at <resources.ExecuteAsTemplate>: error calling ExecuteAsTemplate: type not supported in Resource transformations
1:31:18 PM: ERROR 2020/02/21 13:31:18 render of “page” failed: “/opt/build/repo/themes/Mainroad/layouts/_default/baseof.html:18:55”: execute of template failed: template: _default/single.html:18:55: executing “_default/single.html” at <resources.ExecuteAsTemplate>: error calling ExecuteAsTemplate: type not supported in Resource transformations
1:31:18 PM: Total in 41 ms
1:31:18 PM: Error: Error building site: failed to render pages: render of “home” failed: “/opt/build/repo/themes/Mainroad/layouts/_default/baseof.html:18:55”: execute of template failed: template: index.html:18:55: executing “index.html” at <resources.ExecuteAsTemplate>: error calling ExecuteAsTemplate: type not supported in Resource transformations
1:31:18 PM: Skipping functions preparation step: no functions directory set
1:31:18 PM: Caching artifacts
1:31:18 PM: Started saving pip cache
1:31:18 PM: Finished saving pip cache
1:31:18 PM: Started saving emacs cask dependencies
1:31:18 PM: Finished saving emacs cask dependencies
1:31:18 PM: Started saving maven dependencies
1:31:18 PM: Finished saving maven dependencies
1:31:18 PM: Started saving boot dependencies
1:31:18 PM: Finished saving boot dependencies
1:31:18 PM: Started saving go dependencies
1:31:18 PM: Finished saving go dependencies
1:31:21 PM: Error running command: Build script returned non-zero exit code: 255
1:31:21 PM: Failing build: Failed to build site
1:31:21 PM: failed during stage ‘building site’: Build script returned non-zero exit code: 255
1:31:21 PM: Finished processing build request in 12.824455325s

2

Thanks for doing due diligence in the docs and community- we really appreciate that. You’ve probably seen this already, but if not, you may find some additional “gotchas” in there so it’s worth checking out:

One question is: are you able to build this locally? If so, then I think we can start looking at mismatches with the Netlify build image aside from Hugo, like with npm/yarn, etc. But that’ll be important to know first. If it’s not building locally, there may be incompatibilities between new dependencies and your 0.4x Hugo version (and/or your Mainroad theme).

Let us know what you find!

1 Like
3

Thanks Jen for the supportive response.
To answer your question: Yes, indeed i never lost the ability to build the site locally -so what i eventually did, after some hours of trying to debug this problem with the Netlify build, was the clearly simplest solution, i.e. : create a new Github repo from my local build, and just repoint my Netlify deployment to that new repo. Built without a hitch, and working like a champ ever since.
Lesson learned the hard way: If Netlify should ever fail to build, don’t worry: just rebuild from a different source, even with the same code, and you can be back up & running in the few minutes it takes to clone your repo.

4

Glad to hear you’re up and running, and thanks for sharing your solution :muscle: