debian-forge-composer/internal/worker
Ondřej Budai e4d32f9e2f worker/server: drop the JobResult method
Let's speak why I merged JobResult and JobStatus together:

Both methods actually called jobqueue.JobStatus(), so performance-wise
there's no real difference and it feels to me that it makes the code simpler:
You don't have to decide which method to call, you just get all the data
about a job in one call. We could split those again when we see some perf
issues with retrieving logs on each status check but I don't think we should
optimize prematurely. Let's leave some work for the future us.
2020-05-19 22:20:20 +02:00
..
client.go store: move queue out of the store 2020-05-08 14:53:00 +02:00
json.go store: move queue out of the store 2020-05-08 14:53:00 +02:00
server.go worker/server: drop the JobResult method 2020-05-19 22:20:20 +02:00
server_test.go store: move queue out of the store 2020-05-08 14:53:00 +02:00