No description
0ef89aa864
When restarting composer, we were not handling the compose states correctly. This resolves that as follows: * any running composes are marked as failed, * any waiting composes are put back in the pending jobs queue As a consequence of needing the ability to reinitialize the job queue, we must include the depsolved pipeline in the compose object. This is the correct thing to do, as the semantics we currently adhere to is that pipelines are depsolved when the compose is started (and restarting composer should not affect this by for instance re-depsolve the pipeline). Resolves rhbz#1784062. Signed-off-by: Tom Gundersen <teg@jklm.no> |
||
|---|---|---|
| cmd | ||
| distribution | ||
| internal | ||
| osbuild@e0bb65dd71 | ||
| test | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| .packit.yaml | ||
| .travis.yml | ||
| dnf-json | ||
| go.mod | ||
| go.sum | ||
| golang-github-osbuild-composer.spec | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
osbuild-composer
An image building service based on osbuild. It is inspired by lorax-composer and exposes the same API. As such, it is a drop-in replacement.