-
Bug
-
Resolution: Fixed
-
Blocker
-
None
Problem statement
Following the official documentation, and running
docker volume create jenkins-evergreen-data && \
docker pull jenkins/evergreen:docker-cloud && \
docker run --name evergreen \
--restart=always \
-ti \
-p 8080:80 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v jenkins-evergreen-data:/evergreen/data \
-e LOG_LEVEL=debug \
jenkins/evergreen:docker-cloud
The client fails with to start with the following error :
> evergreen-client@1.0.0 prestart /evergreen/client > tsc sh: tsc: not found npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! evergreen-client@1.0.0 prestart: `tsc` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the evergreen-client@1.0.0 prestart script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Expected behavior
The Evergreen instance should be able to come with a ready to use Jenkins.
It seems like there recent js->typescript migration is responsible for this.
But then we want to understand why our CI did let that go green :-\.
- links to
[JENKINS-53947] Evergreen instance fails to start with "sh: tsc: not found" error
| Description |
New:
h3. Problem statement Following the official documentation, and running {noformat} docker volume create jenkins-evergreen-data && \ docker pull jenkins/evergreen:docker-cloud && \ docker run --name evergreen \ --restart=always \ -ti \ -p 8080:80 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v jenkins-evergreen-data:/evergreen/data \ -e LOG_LEVEL=debug \ jenkins/evergreen:docker-cloud {noformat} The client fails with to start with the following error : |
| Description |
Original:
h3. Problem statement Following the official documentation, and running {noformat} docker volume create jenkins-evergreen-data && \ docker pull jenkins/evergreen:docker-cloud && \ docker run --name evergreen \ --restart=always \ -ti \ -p 8080:80 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v jenkins-evergreen-data:/evergreen/data \ -e LOG_LEVEL=debug \ jenkins/evergreen:docker-cloud {noformat} The client fails with to start with the following error : |
New:
h3. Problem statement Following the official documentation, and running {noformat} docker volume create jenkins-evergreen-data && \ docker pull jenkins/evergreen:docker-cloud && \ docker run --name evergreen \ --restart=always \ -ti \ -p 8080:80 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v jenkins-evergreen-data:/evergreen/data \ -e LOG_LEVEL=debug \ jenkins/evergreen:docker-cloud {noformat} The client fails with to start with the following error : {noformat} > evergreen-client@1.0.0 prestart /evergreen/client > tsc sh: tsc: not found npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! evergreen-client@1.0.0 prestart: `tsc` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the evergreen-client@1.0.0 prestart script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. {noformat} h3. Expected behavior The Evergreen instance should be able to come with a ready to use Jenkins. It seems like there recent js->typescript migration is responsible for this. But then we want to understand why our CI did let that go green :-\. |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Remote Link | New: This issue links to "#309 (Web Link)" [ 21905 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |