778b2de3c0
Two new tests, one for OSBuild and one for Koji jobs. Both follow the same flow: - Enqueue a job that doesn't specify PipelineNames (oldJob) - Enqueue a job that does specify PipelineNames (newJob) - Read the job data for the oldJob and check that the default PipelineNames were added - Read the job data for the newJob and check that it's unchanged - Finish oldJob and add results without specifying PipelineNames - Finish newJob and add results with PipelineNames - Read the oldJob result and check that the default PipelineNames were added - Read the newJob result and check that it's unchanged This is meant to test several scenarios that can occur when upgrading the service: 1. The existing jobqueue has old jobs in it that were queued before the PipelineNames were part of the data structure. The worker should be able to read these and add the fallback data. 2. New jobs are added while old jobs still exist in the queue and the worker can read both types. 3. The existing jobqueue has old finished jobs in it that were finished and had results written before the PipelineNames were part of the result data structure. The worker should be able to read these and add the fallback data. 4. New jobs are finished and results are written while old jobs still exist in the queue and the worker can read both result types. |
||
|---|---|---|
| .. | ||
| api | ||
| client.go | ||
| json.go | ||
| server.go | ||
| server_test.go | ||