How to build chectl outside Che
See original GitHub issueSummary
Because of the situation with #21366, I’m now stuck in a situation where I don’t have a Che cluster deployed and can’t redeploy it. I planned to build the old version myself but found that the documentation expects me to develope chectl only from inside Che; is there any documentation on building it outside of itself?
Relevant information
I tried to run yarn
as instructed, incase that would just work. Here’s the output I got:
yarn install v1.22.18
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ npm run -s postinstall-repositories && npm run -s postinstall-operator && npm run -s postinstall-cleanup
yarn upgrade v1.22.18
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "eslint-config-oclif > eslint-config-xo-space@0.20.0" has incorrect peer dependency "eslint@^5.3.0".
warning "eslint-config-oclif-typescript > @typescript-eslint/eslint-plugin@2.34.0" has incorrect peer dependency "eslint@^5.0.0 || ^6.0.0".
warning "eslint-config-oclif-typescript > @typescript-eslint/parser@2.34.0" has incorrect peer dependency "eslint@^5.0.0 || ^6.0.0".
[5/5] Rebuilding all packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ eclipse-che-operator@0.0.0
info All dependencies
└─ eclipse-che-operator@0.0.0
Done in 7.76s.
internal/fs/utils.js:332
throw err;
^
Error: ENOENT: no such file or directory, lstat '/home/yujiri/chectl/node_modules/eclipse-che-operator/config/samples/org_v1_chebackupserverconfiguration.yaml'
at Object.lstatSync (fs.js:1119:3)
at Object.lstatSync (/home/yujiri/chectl/node_modules/graceful-fs/polyfills.js:307:34)
at statFunc (/home/yujiri/chectl/node_modules/fs-extra/lib/util/stat.js:24:20)
at getStatsSync (/home/yujiri/chectl/node_modules/fs-extra/lib/util/stat.js:25:19)
at Object.checkPathsSync (/home/yujiri/chectl/node_modules/fs-extra/lib/util/stat.js:67:33)
at Object.copySync (/home/yujiri/chectl/node_modules/fs-extra/lib/copy-sync/copy-sync.js:24:38)
at prepareTemplates (/home/yujiri/chectl/prepare-che-operator-templates.js:46:12)
at Object.<anonymous> (/home/yujiri/chectl/prepare-che-operator-templates.js:55:1)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) {
errno: -2,
syscall: 'lstat',
code: 'ENOENT',
path: '/home/yujiri/chectl/node_modules/eclipse-che-operator/config/samples/org_v1_chebackupserverconfiguration.yaml'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command
Issue Analytics
- State:
- Created a year ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
chectl/README.md at main · che-incubator/chectl - GitHub
If you're using linux or macOS, here is how to install chectl by using one single command: For stable channel: $ bash <(curl...
Read more >Introduction to Eclipse Che :: Eclipse Che Documentation
Pre-built stacks with the ability to create custom stacks for any language or runtime. An enterprise integration using OpenShift OAuth or Dex. Browser-based ......
Read more >Newest 'eclipse-che' Questions - Stack Overflow
I am trying to deploy a custom Theia plugin on a Che workspace. The plugin is intended to execute a task on the...
Read more >Pulse · eclipse/che · GitHub
How to build chectl outside Che. #21367 commented on Nov 24, 2022 • 2 new comments. [UD] Devfile editor drops changes on save....
Read more >Burn Eclipse Che to the ground
It even relies on stuff outside of the eclipse-che namespace in your cluster. ... I say "in theory" because in practice nobody could...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually this issue helped me realize that our release actions behave incorrectly. This action [1] is triggered once
.x
branch is created (even before release PR is merged). So, release sources won’t have updatedpackage.json
file.@mkuznyetsov pls have a look.
[1] https://github.com/che-incubator/chectl/blob/0a7174a56b1ce6902613be3243001e25347fa983/.github/workflows/release-build-and-push-to-GH-releases.yml#L18
well, this change has broken the release process because the GH action that creates the release PR needs the branch to exist 😃 will work on a fix…
https://github.com/che-incubator/chectl/actions/runs/3540932049/jobs/5944574155