woodpecker/server/store
6543 e57a09a404
Update pipeline state on server as a whole on approval (#3504)
We can not just update some records for steps, as we want the pipeline
engine as single source of truth but not manage the state.
And the server should only manage the state but not how pipelines work.

We can match the pipeline but neither workflows or steps 1:1, so we
"update" them as a whole by deleting existing workflow and step data and
insert the new info from engine.

close   #3494
close  #3472

---------
*Sponsored by Kithara Software GmbH*

---------

Co-authored-by: Robert Kaussow <xoxys@rknet.org>
2024-03-18 20:07:45 +01:00
..
datastore Update pipeline state on server as a whole on approval (#3504) 2024-03-18 20:07:45 +01:00
mocks Update pipeline state on server as a whole on approval (#3504) 2024-03-18 20:07:45 +01:00
types Return return 404 if registry to delete do not exist (#1278) 2022-10-18 01:48:04 +02:00
common.go Use global logger for xorm logs and add options (#1997) 2023-07-15 01:15:13 +02:00
context.go Remove some interfaces (#3220) 2024-01-19 16:20:35 +01:00
store.go Update pipeline state on server as a whole on approval (#3504) 2024-03-18 20:07:45 +01:00