skoppe / dubster Goto Github PK

The worker itself is run in a docker container. During its lifetime it will create several spin-off containers that either build dmd's or build packages. To facilitate data transfer between them it uses a data container.

During its calls to the docker api it needs to refer to the data container by name. The convention is that the data container is called dubsterdata. However, this fully depends on how the admin named the container during its creation.

A better approach would be to have the worker run an inspect on the container it is in and figure out the name of the data container at the /gen path. And then use that name in subsequent calls to docker.

When running dub test in the worker some packages (due to faulty config) actually start up and never terminate themselves.

Simply watch stdout/stderr and if nothing happens in e.g. 5 min stop container (calling stop on the container will send a sigterm to the process running in the container. If it doesn't respond docker will eventually send sigkill)

forever-d is one package that has this behaviour.

Now if something goes wrong during the http calls to github and code.dlang.org the task that runs the timer to discover new dmds/packages is terminated. Instead we need to catch, log errors and reset the timer.