mistry
mistry copied to clipboard
skroutz
General-purpose build server
### Backend - [x] investigate if we can determine when job has started without looking at the path's mod time. Maybe through `build_result.json`. - [x] properly display `docker build` logs...
Deleting a build in mistry (e.g. for freeing up disk space) is not a straightforward task: 1) it's filesystem-dependent 2) it has to be done with care with regards to...
Similar to the [btrfs adapter](https://github.com/skroutz/mistry/blob/master/pkg/filesystem/btrfs/btrfs.go), we can introduce and support a ZFS adapter.
We already added the job params inside `BuildResult{}` so it might make sense to add the whole job.
This information exists in the BuildInfo struct as of https://github.com/skroutz/mistry/pull/47. The job marshalling should also be updated accordingly.
This could look like this: ```shell $ mistry build --project foo --stream-output Building zxc... Building abc... ```
Currently, clients waiting on an existing pending job are counted as workers as far as the concurrency/backlog limits are concerned. This means that clients that do not really consume any...
We should use a specific label to mark all docker items generated by mistry as such. This label would be used to determine ownership of docker items and allow us...
Currently build workers run concurrently and they execute filesystem operations (rm, stat, ln, mv). This means we might bump onto race conditions where workers of the same build, attempt to...
Right now, there are no limits enforced on how much time a job could take. This might lead to cases where clients wait on a never-ending job, that also consumes...