From b11d31ef23c5dfee6bfa54afbec47fc8b8bab7b1 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sun, 13 May 2018 15:30:23 +0300 Subject: Change: how controller stores persistent data Replace old State class with new FilePersistentState and TransactionalState classes. Use new Resource class instead of raw dicts. Use context managers for creating, updating resources, to avoid mistakes from accidentally not saving changes. Overall persistence should now be rather simpler. This should open up a possibility for changing the controller to insert more actions into the build graph, to trigger notifcations via the workers. --- yarns/500-build-fail.yarn | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) (limited to 'yarns/500-build-fail.yarn') diff --git a/yarns/500-build-fail.yarn b/yarns/500-build-fail.yarn index 79d4be6..59a2e67 100644 --- a/yarns/500-build-fail.yarn +++ b/yarns/500-build-fail.yarn @@ -73,8 +73,7 @@ Register a worker. Trigger build. - WHEN user makes request PUT /projects/rome/status - ... with a valid token and body { "status": "triggered" } + WHEN user makes request GET /projects/rome/+trigger THEN result has status code 200 Worker wants work and gets the first step to run. @@ -127,13 +126,7 @@ User sees changed status. ... "doing": {} ... } -The pipeline status indicates it's idle. - - WHEN user makes request GET /projects/rome/status - THEN result has status code 200 - AND body matches { "status": "idle" } - -Also, there's a build with a log. +There's a build with a log. WHEN user makes request GET /builds THEN result has status code 200 -- cgit v1.2.1