-
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