debian-forge-composer/internal
Tom Gundersen 0ef89aa864 store: fix compose state handling on restart
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>
2019-12-17 21:49:11 +01:00
..
blueprint blueprints: fix group handling 2019-12-17 09:24:15 +01:00
crypt blueprint: add support for unencrypted passwords in user customization 2019-10-31 21:46:39 +01:00
distro distro: rename openstack and vmdk images to match lorax 2019-12-16 01:32:41 +01:00
jobqueue worker: wrap errors, adding descriptions 2019-12-15 22:05:31 +01:00
mocks/rpmmd distro: set the repository checksum dynamically 2019-12-10 20:38:22 +01:00
pipeline pipeline/stage/grub2: support explicit legacy/uefi API 2019-12-14 17:23:31 +01:00
rpmmd rpmmd: add IgnoreSSL key to RepoConfig 2019-12-12 01:27:04 +00:00
store store: fix compose state handling on restart 2019-12-17 21:49:11 +01:00
target target: add new fields to target and cleanup 2019-12-01 00:05:17 +01:00
test test: introduce helpers for go-cmp 2019-12-01 00:05:17 +01:00
upload Introduce Azure upload test 2019-11-29 12:19:40 +01:00
weldr store: fix compose state handling on restart 2019-12-17 21:49:11 +01:00