Screwdriver: Build looks stuck if docker pull takes long
Builds look stuck with no logs or status messages for a while if I specify a large docker image to screwdriver.yaml.
They are actually pulling the docker image in the background, so it would be better if UI shows us a message or a log about preparation of the build at that time.
catto
All 2 comments
I agree, this has always bothered me. There are two issues going on here, depending on your execution engine.
- Docker Swarm execution calls are synchronous and can be slow. Docker swarm will make a Pull first then a Create. This call will take as long as the pull takes.
- Kubernetes calls have to way to report back asynchronous statuses (like downloading image, waiting for available machine, etc.).
We're hoping that we can solve that when we get to https://github.com/screwdriver-cd/screwdriver/issues/431. We should be able to make all execution calls async (adding to the queue) and then have the engines themselves report back statuses on a regular basis (enqueued for X time, waiting for resources, downloading, etc.).
stjohnjohnson
on 27 Jan 2017
This should be solved by https://github.com/screwdriver-cd/ui/pull/251
d2lam
on 6 Apr 2018
Related issues
yoshwata
路
5Comments
wahapo
路
7Comments
yoshwata
路
5Comments
jeffreytolar
路
3Comments
yokawara
路
5Comments
Most helpful comment
I agree, this has always bothered me. There are two issues going on here, depending on your execution engine.
We're hoping that we can solve that when we get to https://github.com/screwdriver-cd/screwdriver/issues/431. We should be able to make all execution calls async (adding to the queue) and then have the engines themselves report back statuses on a regular basis (enqueued for X time, waiting for resources, downloading, etc.).