Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Build fail with Circle CI at build step #55

Closed
jimni1222 opened this issue Aug 13, 2019 · 0 comments · Fixed by #56
Closed

Build fail with Circle CI at build step #55

jimni1222 opened this issue Aug 13, 2019 · 0 comments · Fixed by #56
Assignees
Labels
issue/bug Issues with the code-level bugs. open/approved The issue is confirmed as being a bug to be fixed or enhancement to be developed.

Comments

@jimni1222
Copy link
Contributor

Describe the bug
I added build step in workflow_publish, but there is no install step in there.
So "sh: 1: gulp: not found" error is occured.

How to reproduce
Try to publish caver-js module through circle ci.

Expected behavior
caver-js can be published successfully without error.

Attachments
If applicable, add data, logs or screenshots to help explain your problem.

Environment (please complete the following information)

  • caver-js v1.0.1-rc.10
  • macOS/10.14

Additional context
Error in Circle CI

#!/bin/bash -eo pipefail
npm run build

caver-js@1.0.0 build /home/circleci/repo
gulp default

sh: 1: gulp: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! caver-js@1.0.0 build: gulp default
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the caver-js@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR! /home/circleci/.npm/_logs/2019-08-13T05_17_41_347Z-debug.log
Exited with code 1

@jimni1222 jimni1222 added open/approved The issue is confirmed as being a bug to be fixed or enhancement to be developed. issue/bug Issues with the code-level bugs. labels Aug 13, 2019
@jimni1222 jimni1222 self-assigned this Aug 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/bug Issues with the code-level bugs. open/approved The issue is confirmed as being a bug to be fixed or enhancement to be developed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant