search

iamraviprakash / quickgram-web

Quick and disposable way to communicate with anyone anonymously. Create, use and delete room as you wish.
https://quickgram.netlify.app
1 stars 0 forks source link

[FIX] Netlify automated build and deploy #9

Closed iamraviprakash closed 1 year ago

iamraviprakash commented 1 year ago 
10:54:59 AM: Build ready to start
10:55:06 AM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
10:55:06 AM: build-image tag: v4.10.1
10:55:06 AM: buildbot version: 2a8b421219da5ccbdc68429ef8a83ca0b63d4f78
10:55:06 AM: Fetching cached dependencies
10:55:06 AM: Failed to fetch cache, continuing with build
10:55:06 AM: Starting to prepare the repo for build
10:55:06 AM: No cached dependencies found. Cloning fresh repo
10:55:06 AM: git clone git@github.com:iamraviprakash/glitchgram-web
10:55:07 AM: Preparing Git Reference refs/heads/master
10:55:07 AM: Parsing package.json dependencies
10:55:08 AM: Starting build script
10:55:08 AM: Installing dependencies
10:55:08 AM: Python version set to 2.7
10:55:09 AM: v16.16.0 is already installed.
10:55:09 AM: Now using node v16.16.0 (npm v8.11.0)
10:55:09 AM: Started restoring cached build plugins
10:55:09 AM: Finished restoring cached build plugins
10:55:09 AM: Attempting ruby version 2.7.2, read from environment
10:55:10 AM: Using ruby version 2.7.2
10:55:10 AM: Using PHP version 8.0
10:55:11 AM: No npm workspaces detected
10:55:11 AM: Started restoring cached node modules
10:55:11 AM: Finished restoring cached node modules
10:55:11 AM: Installing NPM modules using NPM version 8.11.0
10:55:11 AM: npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
10:55:11 AM: npm WARN config location in the cache, and they are managed by
10:55:11 AM: npm WARN config     [`cacache`](http://npm.im/cacache).
10:55:11 AM: npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
10:55:11 AM: npm WARN config location in the cache, and they are managed by
10:55:11 AM: npm WARN config     [`cacache`](http://npm.im/cacache).
10:55:17 AM: npm WARN ERESOLVE overriding peer dependency
10:55:17 AM: npm WARN ERESOLVE overriding peer dependency
10:55:22 AM: npm WARN EBADENGINE Unsupported engine {
10:55:22 AM: npm WARN EBADENGINE   package: 'glitchgram@1.0.0',
10:55:22 AM: npm WARN EBADENGINE   required: { node: '12.18.x' },
10:55:22 AM: npm WARN EBADENGINE   current: { node: 'v16.16.0', npm: '8.11.0' }
10:55:22 AM: npm WARN EBADENGINE }
10:55:27 AM: npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
10:55:29 AM: npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
10:55:42 AM: added 388 packages, and audited 389 packages in 31s
10:55:42 AM: 80 packages are looking for funding
10:55:42 AM:   run `npm fund` for details
10:55:42 AM: found 0 vulnerabilities
10:55:42 AM: NPM modules installed
10:55:43 AM: npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
10:55:43 AM: npm WARN config location in the cache, and they are managed by
10:55:43 AM: npm WARN config     [`cacache`](http://npm.im/cacache).
10:55:43 AM: Started restoring cached go cache
10:55:43 AM: Finished restoring cached go cache
10:55:43 AM: Installing Go version 1.17 (requested 1.17)
10:55:48 AM: unset GOOS;
10:55:48 AM: unset GOARCH;
10:55:48 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.17.linux.amd64';
10:55:48 AM: export PATH="/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}";
10:55:48 AM: go version >&2;
10:55:48 AM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.17.linux.amd64.env"
10:55:48 AM: go version go1.17 linux/amd64
10:55:48 AM: Installing missing commands
10:55:48 AM: Verify run directory
10:55:49 AM: ​
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM:   Netlify Build                                                 
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM: ​
10:55:49 AM: ❯ Version
10:55:49 AM:   @netlify/build 27.11.3
10:55:49 AM: ​
10:55:49 AM: ❯ Flags
10:55:49 AM:   baseRelDir: true
10:55:49 AM:   buildId: 62f9d8aa489dcc000845410c
10:55:49 AM:   deployId: 62f9d8aa489dcc000845410e
10:55:49 AM: ​
10:55:49 AM: ❯ Current directory
10:55:49 AM:   /opt/build/repo
10:55:49 AM: ​
10:55:49 AM: ❯ Config file
10:55:49 AM:   /opt/build/repo/netlify.toml
10:55:49 AM: ​
10:55:49 AM: ❯ Context
10:55:49 AM:   production
10:55:49 AM: ​
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM:   1. build.command from netlify.toml                            
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM: ​
10:55:49 AM: $ vite build
10:55:49 AM: vite v2.9.15 building for production...
10:55:49 AM: transforming...
10:55:49 AM: ✓ 13 modules transformed.
10:55:49 AM: [vite:load-fallback] Could not load /opt/build/repo/src/Config (imported by src/index.jsx): ENOENT: no such file or directory, open '/opt/build/repo/src/Config'
10:55:49 AM: error during build:
10:55:49 AM: Error: Could not load /opt/build/repo/src/Config (imported by src/index.jsx): ENOENT: no such file or directory, open '/opt/build/repo/src/Config'
10:55:49 AM: ​
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM:   "build.command" failed                                        
10:55:49 AM: ────────────────────────────────────────────────────────────────
10:55:49 AM: ​
10:55:49 AM:   Error message
10:55:49 AM:   Command failed with exit code 1: vite build (https://ntl.fyi/exit-code-1)
10:55:49 AM: ​
10:55:49 AM:   Error location
10:55:49 AM:   In build.command from netlify.toml:
10:55:49 AM:   vite build
10:55:49 AM: ​
10:55:49 AM:   Resolved config
10:55:49 AM:   build:
10:55:49 AM:     command: vite build
10:55:49 AM:     commandOrigin: config
10:55:51 AM: Creating deploy upload records
10:55:49 AM:     environment:
10:55:49 AM:       - ONEGRAPH_AUTHLIFY_TOKEN
10:55:49 AM:     publish: /opt/build/repo/dist
10:55:49 AM:     publishOrigin: config
10:55:51 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
10:55:49 AM:   functionsDirectory: /opt/build/repo/netlify/functions
10:55:50 AM: Caching artifacts
10:55:50 AM: Started saving node modules
10:55:50 AM: Finished saving node modules
10:55:50 AM: Started saving build plugins
10:55:50 AM: Finished saving build plugins
10:55:50 AM: Started saving pip cache
10:55:50 AM: Finished saving pip cache
10:55:50 AM: Started saving emacs cask dependencies
10:55:50 AM: Finished saving emacs cask dependencies
10:55:50 AM: Started saving maven dependencies
10:55:50 AM: Finished saving maven dependencies
10:55:50 AM: Started saving boot dependencies
10:55:50 AM: Finished saving boot dependencies
10:55:50 AM: Started saving rust rustup cache
10:55:50 AM: Finished saving rust rustup cache
10:55:50 AM: Started saving go dependencies
10:55:50 AM: Finished saving go dependencies
10:55:51 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
10:55:51 AM: Failing build: Failed to build site
10:55:51 AM: Finished processing build request in 45.58229962s

Not able to do automated deploy due build error

iamraviprakash commented 1 year ago

It happened because git config core.ignorecase wasn't set to false. Due to this src/config and src/Config was treated same.