-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Gitlab CI issue #646
Comments
Ok that seemed to be a network error that just occured a lot of times. Maybe a load balancing issue on node side since I tried a lot of times to fix the pipeline. Now I get:
|
Wow, this works. I just had to explicitly set the shell due to no $SHELL available in CI context. .workspace:
image: debian:latest
before_script: &install_pnpm
- apt-get update -y && apt-get install -y git unzip gzip xz-utils curl
- curl -fsSL https://moonrepo.dev/install/proto.sh | bash -s -- latest --shell=bash --yes
- source $HOME/.profile && proto install
- pnpm config set store-dir .cache/pnpm-store
- pnpm --silent install |
Nice find! This should fallback to If possible, the command that errors with "No such file or directory", can you run it with |
Yeah this would hard error if no shell is found: https://github.com/moonrepo/proto/blob/master/crates/cli/src/commands/setup.rs#L65 |
Maybe using this helper would work out? https://github.com/moonrepo/starbase/blob/master/crates/shell/src/shell.rs#L59 |
It does use that helper. |
What version?
0.41.7
Which command?
proto install
What happened?
I am using the following script to install proto in our Gitlab pipelines. Unfortunately it fails pulling node. Is there a recommend way of using proto in other CI env?
Trace logs?
Operating system?
Linux
Architecture?
x64
The text was updated successfully, but these errors were encountered: