-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to fix event.json cannot found issue when I run pnpm install
in CodeBuild?
#127
Comments
I am not familiar with pnpm. could you check if this helps? https://github.com/pnpm/pnpm.github.io/issues/296 |
same issue. I am converting the trigger from a Lambda function to a Github Action. Both are calling the exact same Codebuild project. But Lambda calling works, Github Action calling will result in this node:fs / event.json not found error. The only difference seems to be Github Action > aws-codebuild-run-build@v1 is passing a lot of GITHUB_* variables. The particular file that is causing trouble seems to be Is there a way to NOT pass all the GITHUB_* variables? |
Hi @yiyang-ampup, Thanks for the finding. This is expected behavior today. According to the specs,
No. But we can introduce a new Your contributions via a. pull request will be much appreciated https://github.com/aws-actions/aws-codebuild-run-build/blob/main/CONTRIBUTING.md |
I am experiencing the same issue. When I run manually in the Codebuild console with the same sha, this error does not occur. I am not changing the buildspec or doing any manual changes. Commenting to follow this issue.
|
@vitulrana has addressed this feature request. see: #142 |
Hi guys, I got this error when I run
pnpm install
in CodeBuild. Seems that pnpm cannot found the GitHub event.json when install.Is there any way to fix or ignore this?
Cheers!
113 | [Container] 2023/03/01 04:59:07 Running command pnpm install
114 | node:fs:585
115 | handleErrorFromBinding(ctx);
116 | ^
117 |
118 | Error: ENOENT: no such file or directory, open '/home/runner/work/_temp/_github_workflow/event.json'
119 | at Object.openSync (node:fs:585:3)
120 | at Object.readFileSync (node:fs:453:35)
121 | at NodeFS.readFileSync (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:84834:28)
122 | at NodeFS.readJsonSync (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:84171:30)
123 | at ../node_modules/.pnpm/@yarnpkg[email protected][email protected]/node_modules/@yarnpkg/core/lib/Configuration.js (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:160610:117)
124 | at __require (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:12:50)
125 | at ../node_modules/.pnpm/@yarnpkg[email protected][email protected]/node_modules/@yarnpkg/core/lib/execUtils.js (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:161970:27)
126 | at __require (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:12:50)
127 | at ../node_modules/.pnpm/@yarnpkg[email protected][email protected]/node_modules/@yarnpkg/core/lib/index.js (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:174430:43)
128 | at __require (/usr/local/lib/node_modules/pnpm/dist/pnpm.cjs:12:50) {
129 | errno: -2,
130 | syscall: 'open',
131 | code: 'ENOENT',
132 | path: '/home/runner/work/_temp/_github_workflow/event.json'
133 | }
134 |
135 | [Container] 2023/03/01 04:59:07 Command did not exit successfully pnpm install exit status 1
136 | [Container] 2023/03/01 04:59:07 Phase complete: BUILD State: FAILED
137 | [Container] 2023/03/01 04:59:07 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: pnpm install. Reason: exit status 1
The text was updated successfully, but these errors were encountered: