Open ptoseklukas opened 4 years ago
Hi @ptoseklukas, Our starter uses. Gatsby Incremental Builds, to take advantage of that enable build plugin in netlify. follow these instruction https://docs.netlify.com/configure-builds/build-plugins/, let me know if this resolves the issue.
Hello,
I use this starter at netlify and when I add new post everytime build crash. I delete all post and still build failing.
My repo: https://github.com/ptoseklukas/gatsby-starter-delog
Build log bellow.
3:14:43 PM: Waiting for other deploys from your team to complete 3:14:56 PM: Build ready to start 3:14:58 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774 3:14:58 PM: build-image tag: v3.3.7 3:14:58 PM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681 3:14:58 PM: Fetching cached dependencies 3:14:58 PM: Starting to download cache of 264.6MB 3:14:59 PM: Finished downloading cache in 1.1476683s 3:14:59 PM: Starting to extract cache 3:15:11 PM: Finished extracting cache in 11.561703312s 3:15:11 PM: Finished fetching cache in 13.034144519s 3:15:11 PM: Starting to prepare the repo for build 3:15:12 PM: Preparing Git Reference refs/heads/master 3:15:12 PM: Found Netlify configuration file netlify.toml in site root 3:15:12 PM: Found Netlify configuration file(s). Overriding site configuration 3:15:12 PM: Starting build script 3:15:12 PM: Installing dependencies 3:15:13 PM: Started restoring cached node version 3:15:18 PM: Finished restoring cached node version 3:15:18 PM: Attempting node version '10' from .nvmrc 3:15:19 PM: v10.20.1 is already installed. 3:15:19 PM: Now using node v10.20.1 (npm v6.14.4) 3:15:20 PM: Attempting ruby version 2.6.2, read from environment 3:15:21 PM: Using ruby version 2.6.2 3:15:21 PM: Using PHP version 5.6 3:15:21 PM: Started restoring cached node modules 3:15:21 PM: Finished restoring cached node modules 3:15:22 PM: Started restoring cached go cache 3:15:22 PM: Finished restoring cached go cache 3:15:22 PM: unset GOOS; 3:15:22 PM: unset GOARCH; 3:15:22 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64'; 3:15:22 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}"; 3:15:22 PM: go version >&2; 3:15:22 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env'; 3:15:22 PM: go version go1.12 linux/amd64 3:15:22 PM: Installing missing commands 3:15:22 PM: Verify run directory 3:15:22 PM: Executing user command: npm run build 3:15:22 PM: > gatsby-starter-delog@1.6.0 build /opt/build/repo 3:15:22 PM: > GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages 3:15:25 PM: success open and validate gatsby-configs - 0.085s 3:15:26 PM: success load plugins - 0.852s 3:15:26 PM: success onPreInit - 0.014s 3:15:26 PM: success initialize cache - 0.010s 3:15:26 PM: success copy gatsby files - 0.035s 3:15:26 PM: success onPreBootstrap - 0.004s 3:15:26 PM: success createSchemaCustomization - 0.016s 3:15:26 PM: error 3:15:26 PM: The path passed to gatsby-source-filesystem does not exist on your file system: 3:15:26 PM: /opt/build/repo/_data 3:15:26 PM: Please pick a path to an existing directory. 3:15:26 PM: See docs here - https://www.gatsbyjs.org/packages/gatsby-source-filesystem/ 3:15:26 PM: not finished source and transform nodes - 0.034s 3:15:26 PM: npm 3:15:26 PM: ERR! code 3:15:26 PM: ELIFECYCLE 3:15:26 PM: npm 3:15:26 PM: ERR! 3:15:26 PM: errno 3:15:26 PM: 1 3:15:26 PM: npm 3:15:26 PM: ERR! 3:15:26 PM: gatsby-starter-delog@1.6.0 build:
GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
3:15:26 PM: npm 3:15:26 PM: ERR! 3:15:26 PM: Exit status 1 3:15:26 PM: npm 3:15:26 PM: ERR! 3:15:26 PM: npm 3:15:26 PM: ERR! Failed at the gatsby-starter-delog@1.6.0 build script. 3:15:26 PM: npm 3:15:26 PM: ERR! 3:15:26 PM: This is probably not a problem with npm. There is likely additional logging output above. 3:15:26 PM: npm 3:15:26 PM: ERR! A complete log of this run can be found in: 3:15:26 PM: npm ERR! /opt/buildhome/.npm/_logs/2020-05-06T13_15_26_416Z-debug.log 3:15:26 PM: Skipping functions preparation step: no functions directory set 3:15:26 PM: Caching artifacts 3:15:26 PM: Started saving node modules 3:15:26 PM: Finished saving node modules 3:15:26 PM: Started saving pip cache 3:15:26 PM: Finished saving pip cache 3:15:26 PM: Started saving emacs cask dependencies 3:15:26 PM: Finished saving emacs cask dependencies 3:15:26 PM: Started saving maven dependencies 3:15:26 PM: Finished saving maven dependencies 3:15:26 PM: Started saving boot dependencies 3:15:26 PM: Finished saving boot dependencies 3:15:26 PM: Started saving go dependencies 3:15:26 PM: Finished saving go dependencies 3:15:26 PM: Error running command: Build script returned non-zero exit code: 1 3:15:26 PM: Failing build: Failed to build site 3:15:26 PM: failed during stage 'building site': Build script returned non-zero exit code: 1 3:15:26 PM: Finished processing build request in 28.613844152sOnly one my post
3:19:55 PM: Build ready to start 3:19:56 PM: build-image version: 2dbd444fcdce00cf06325060a8238d5ae3e86774 3:19:56 PM: build-image tag: v3.3.7 3:19:56 PM: buildbot version: d305548225ac57bb00eb5a596b0b8674e76a4681 3:19:56 PM: Fetching cached dependencies 3:19:56 PM: Starting to download cache of 264.6MB 3:19:58 PM: Finished downloading cache in 1.192874943s 3:19:58 PM: Starting to extract cache 3:20:09 PM: Finished extracting cache in 11.348739879s 3:20:09 PM: Finished fetching cache in 12.615367904s 3:20:09 PM: Starting to prepare the repo for build 3:20:09 PM: Preparing Git Reference refs/heads/master 3:20:10 PM: Found Netlify configuration file netlify.toml in site root 3:20:10 PM: Found Netlify configuration file(s). Overriding site configuration 3:20:10 PM: Starting build script 3:20:10 PM: Installing dependencies 3:20:11 PM: Started restoring cached node version 3:20:15 PM: Finished restoring cached node version 3:20:15 PM: Attempting node version '10' from .nvmrc 3:20:15 PM: v10.20.1 is already installed. 3:20:16 PM: Now using node v10.20.1 (npm v6.14.4) 3:20:16 PM: Attempting ruby version 2.6.2, read from environment 3:20:18 PM: Using ruby version 2.6.2 3:20:18 PM: Using PHP version 5.6 3:20:18 PM: Started restoring cached node modules 3:20:18 PM: Finished restoring cached node modules 3:20:18 PM: Started restoring cached go cache 3:20:18 PM: Finished restoring cached go cache 3:20:18 PM: unset GOOS; 3:20:18 PM: unset GOARCH; 3:20:18 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64'; 3:20:18 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}"; 3:20:18 PM: go version >&2; 3:20:18 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env'; 3:20:18 PM: go version go1.12 linux/amd64 3:20:18 PM: Installing missing commands 3:20:18 PM: Verify run directory 3:20:18 PM: Executing user command: npm run build 3:20:19 PM: > gatsby-starter-delog@1.6.0 build /opt/build/repo 3:20:19 PM: > GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages 3:20:21 PM: success open and validate gatsby-configs - 0.076s 3:20:22 PM: success load plugins - 0.872s 3:20:22 PM: success onPreInit - 0.011s 3:20:22 PM: success initialize cache - 0.008s 3:20:22 PM: success copy gatsby files - 0.029s 3:20:22 PM: success onPreBootstrap - 0.003s 3:20:22 PM: success createSchemaCustomization - 0.016s 3:20:22 PM: success source and transform nodes - 0.104s 3:20:23 PM: success building schema - 0.300s 3:20:23 PM: error There was an error in your GraphQL query: 3:20:23 PM: Cannot query field "path" on type "MarkdownRemarkFrontmatter". 3:20:23 PM: If you don't expect "path" to exist on the type "MarkdownRemarkFrontmatter" it is most likely a typo. 3:20:23 PM: However, if you expect "path" to exist there are a couple of solutions to common problems: 3:20:23 PM: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server 3:20:23 PM: - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have 3:20:23 PM: - You want to optionally use your field "path" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") 3:20:23 PM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "MarkdownRemarkFrontmatter": 3:20:23 PM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions 3:20:23 PM: not finished createPages - 0.033s 3:20:23 PM: npm 3:20:23 PM: ERR! code ELIFECYCLE 3:20:23 PM: npm 3:20:23 PM: ERR! errno 1 3:20:23 PM: npm ERR! 3:20:23 PM: gatsby-starter-delog@1.6.0 build:
GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages
3:20:23 PM: npm 3:20:23 PM: ERR! Exit status 1 3:20:23 PM: npm ERR! 3:20:23 PM: npm 3:20:23 PM: ERR! Failed at the gatsby-starter-delog@1.6.0 build script. 3:20:23 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 3:20:23 PM: npm 3:20:23 PM: ERR! A complete log of this run can be found in: 3:20:23 PM: npm 3:20:23 PM: ERR! /opt/buildhome/.npm/_logs/2020-05-06T13_20_23_119Z-debug.log 3:20:23 PM: Skipping functions preparation step: no functions directory set 3:20:23 PM: Caching artifacts 3:20:23 PM: Started saving node modules 3:20:23 PM: Finished saving node modules 3:20:23 PM: Started saving pip cache 3:20:23 PM: Finished saving pip cache 3:20:23 PM: Started saving emacs cask dependencies 3:20:23 PM: Finished saving emacs cask dependencies 3:20:23 PM: Started saving maven dependencies 3:20:23 PM: Finished saving maven dependencies 3:20:23 PM: Started saving boot dependencies 3:20:23 PM: Finished saving boot dependencies 3:20:23 PM: Started saving go dependencies 3:20:23 PM: Finished saving go dependencies 3:20:23 PM: Error running command: Build script returned non-zero exit code: 1 3:20:23 PM: Failing build: Failed to build site 3:20:23 PM: failed during stage 'building site': Build script returned non-zero exit code: 1 3:20:23 PM: Finished processing build request in 26.730408558s