1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
Running jobs
============
This chapter contains tests that verify that WEBAPP schedules jobs,
accepts job output, and lets the admin kill running jobs.
Run a job successfully
----------------------
To start with, with an empty run-queue, nothing should be scheduled.
SCENARIO run a job
GIVEN a new git repository in CONFGIT
AND an empty lorry-controller.conf in CONFGIT
AND lorry-controller.conf in CONFGIT adds lorries *.lorry using prefix upstream
AND WEBAPP uses CONFGIT as its configuration directory
AND a running WEBAPP
WHEN admin makes request GET /1.0/give-me-job
THEN response has job_id set to null
WHEN admin makes request GET /1.0/list-running-jobs
THEN response has running_jobs set to []
Add a Lorry spec to the run-queue, and request a job. We still
shouldn't get a job, since the queue isn't set to run yet.
GIVEN Lorry file CONFGIT/foo.lorry with {"foo":{"type":"git","url":"git://foo"}}
WHEN admin makes request GET /1.0/read-configuration
AND admin makes request GET /1.0/give-me-job
THEN response has job_id set to null
Enable the queue, and off we go.
WHEN admin makes request GET /1.0/start-queue
AND admin makes request GET /1.0/give-me-job
THEN response has job_id set to 1
AND response has path set to "upstream/foo"
WHEN admin makes request GET /1.0/lorry/upstream/foo
THEN response has running_job set to 1
Requesting another job should now again return null.
WHEN admin makes request GET /1.0/give-me-job
THEN response has job_id set to null
Inform WEBAPP the job is finished.
WHEN MINION makes request POST /1.0/job-update with job_id=1&exit=0
THEN response has kill_job set to false
WHEN admin makes request GET /1.0/lorry/upstream/foo
THEN response has running_job set to null
Cleanup.
FINALLY WEBAPP terminates
Stop job in the middle
----------------------
We need to be able to stop jobs while they're running as well. We
start by setting up everything so that a job is running, the same way
we did for the successful job scenario.
SCENARIO stop a job while it's running
GIVEN a new git repository in CONFGIT
AND an empty lorry-controller.conf in CONFGIT
AND lorry-controller.conf in CONFGIT adds lorries *.lorry using prefix upstream
AND WEBAPP uses CONFGIT as its configuration directory
AND a running WEBAPP
AND Lorry file CONFGIT/foo.lorry with {"foo":{"type":"git","url":"git://foo"}}
WHEN admin makes request GET /1.0/read-configuration
AND admin makes request GET /1.0/start-queue
AND admin makes request GET /1.0/give-me-job
THEN response has job_id set to 1
AND response has path set to "upstream/foo"
Admin will now ask WEBAPP to kill the job. This changes sets a field
in the STATEDB only.
WHEN admin makes request POST /1.0/stop-job with job_id=1
AND admin makes request GET /1.0/lorry/upstream/foo
THEN response has kill_job set to true
Now, when MINION updates the job, WEBAPP will tell it to kill it.
MINION will do so, and then update the job again.
WHEN MINION makes request POST /1.0/job-update with job_id=1&exit=no
THEN response has kill_job set to true
WHEN MINION makes request POST /1.0/job-update with job_id=1&exit=1
Admin will now see that the job has, indeed, been killed.
WHEN admin makes request GET /1.0/lorry/upstream/foo
THEN response has running_job set to null
WHEN admin makes request GET /1.0/list-running-jobs
THEN response has running_jobs set to []
Cleanup.
FINALLY WEBAPP terminates
|
