Netifly build site failing with the following error using Github, Hugo, Forrestry.io

PLEASE help us help you by writing a good post!

1:05:34 PM: Build ready to start
1:05:36 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774
1:05:36 PM: build-image tag: v3.3.7
1:05:36 PM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681
1:05:36 PM: Fetching cached dependencies
1:05:36 PM: Starting to download cache of 254.9KB
1:05:36 PM: Finished downloading cache in 65.826073ms
1:05:36 PM: Starting to extract cache
1:05:36 PM: Failed to fetch cache, continuing with build
1:05:36 PM: Starting to prepare the repo for build
1:05:37 PM: No cached dependencies found. Cloning fresh repo
1:05:37 PM: git clone GitHub - Hal-Black/utba-dev1
1:05:38 PM: Preparing Git Reference refs/heads/master
1:05:38 PM: Found Netlify configuration file netlify.toml in site root
1:05:38 PM: Found Netlify configuration file(s). Overriding site configuration
1:05:38 PM: Different build command detected, going to use the one specified in the Netlify configuration file: ‘./stackbit-build.sh’ versus ‘hugo_0.47’ in the Netlify UI
1:05:38 PM: Starting build script
1:05:38 PM: Installing dependencies
1:05:39 PM: Downloading and installing node v10.20.1…
1:05:40 PM: Downloading https://nodejs.org/dist/v10.20.1/node-v10.20.1-linux-x64.tar.xz
1:05:40 PM:
##############################
1:05:40 PM: 42.2%
1:05:40 PM:
######################################
1:05:40 PM: ################################## 100.0%
1:05:40 PM: Computing checksum with sha256sum
1:05:40 PM: Checksums matched!
1:05:43 PM: Now using node v10.20.1 (npm v6.14.4)
1:05:43 PM: Attempting ruby version 2.6.2, read from environment
1:05:44 PM: Using ruby version 2.6.2
1:05:44 PM: Using PHP version 5.6
1:05:44 PM: Installing Hugo 0.47
1:05:45 PM: Hugo Static Site Generator v0.47/extended linux/amd64 BuildDate: 2018-08-17T09:29:31Z
1:05:45 PM: Started restoring cached go cache
1:05:45 PM: Finished restoring cached go cache
1:05:45 PM: unset GOOS;
1:05:45 PM: unset GOARCH;
1:05:45 PM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.12.linux.amd64’;
1:05:45 PM: export PATH=“/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}”;
1:05:45 PM: go version >&2;
1:05:45 PM: export GIMME_ENV=‘/opt/buildhome/.gimme/env/go1.12.linux.amd64.env’;
1:05:45 PM: go version go1.12 linux/amd64
1:05:45 PM: Installing missing commands
1:05:45 PM: Verify run directory
1:05:45 PM: Executing user command: ./stackbit-build.sh
1:05:45 PM: /usr/local/bin/build: line 45: ./stackbit-build.sh: Permission denied
1:05:45 PM: Skipping functions preparation step: no functions directory set
1:05:45 PM: Caching artifacts
1:05:45 PM: Started saving pip cache
1:05:45 PM: Finished saving pip cache
1:05:45 PM: Started saving emacs cask dependencies
1:05:46 PM: Finished saving emacs cask dependencies
1:05:46 PM: Started saving maven dependencies
1:05:46 PM: Finished saving maven dependencies
1:05:46 PM: Started saving boot dependencies
1:05:46 PM: Finished saving boot dependencies
1:05:46 PM: Started saving go dependencies
1:05:46 PM: Finished saving go dependencies
1:05:50 PM: Error running command: Build script returned non-zero exit code: 126
1:05:50 PM: Failing build: Failed to build site
1:05:50 PM: failed during stage ‘building site’: Build script returned non-zero exit code: 126
1:05:50 PM: Finished processing build request in 13.830557606s

interesting - are you trying to deploy a repo that was created by stackbit?

As in: did you create this project on stackbit, and then clone down the repo, and now you are trying to deploy it somewhere else?

Hi
First, thanks for looking at this issue.
Someone else created the repo using stackbit.
I cloned it using Windows (did not fork) as a zip file.
I have now hosted it on Github Hal-Black · GitHub as utba-dev1

Part of the README.md has the following:

Stackbit Libris Theme

This site was generated by www.stackbit.com, v0.2.82.
Stackbit Libris Theme original README is located here.
The content of this site is managed by Forestry. Visit https://forestry.io to manage site content.

hey there,

It might be possible to get this to work, but there is a big chance this is going to be fairly tricky - you’ll have to rewrite things, get an API key, all that jazz. This isn’t really how stackbit is supposed to work.

Given that you can just re-create what you are trying to do via the stackbit ui, is there a compelling reason to do it this way?

If you are just looking for a simple starter using hugo and forestry, you can click that together in a few minutes on Stackbit, as opposed manually editing things to work in the format they need to for a manual deploy this way.

Hi
Thanks for the update.
I will now try JAMStack Tutorial: Set up a website with no coding for $0 [Step by step]

Regards,
Hal

1 Like