Following the official documentation, and running
docker volume create jenkins-evergreen-data && \
docker pull jenkins/evergreen:docker-cloud && \
docker run --name evergreen \
-p 8080:80 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v jenkins-evergreen-data:/evergreen/data \
-e LOG_LEVEL=debug \
The client fails with to start with the following error :
> firstname.lastname@example.org prestart /evergreen/client
sh: tsc: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! email@example.com prestart: `tsc`
npm ERR! spawn ENOENT
npm ERR! Failed at the firstname.lastname@example.org prestart script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
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 :-\.