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
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
|
Building a project
=============================================================================
One build, one worker
-----------------------------------------------------------------------------
This section uses the controller to walk through all the steps for a
build. We start with some setup, defining a git repo and an ick
project and starting the controller.
SCENARIO run a build with one worker
GIVEN a git repo foo.git with file index.mdwn containing
... "hello, world\n"
AND a project foo, using foo.git, publishing to foo-web
AND a running controller instance
Ensure controller knows of the project.
WHEN user calls GET /projects
THEN response has status 200,
... and JSON body "{ "projects": [ "foo" ] }"
There is no job running now, so if the worker manager asks for work,
it gets nothing.
WHEN worker manager calls GET /worker/bar
THEN response has status 200, and an empty body
Trigger a new build. There is now work to do.
WHEN git server calls GET /projects/foo/+trigger
THEN response has status 200
WHEN worker manager calls GET /worker/bar
THEN response has status 200, and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "ikiwiki --build"
... }"
Pretend a job is running, and send output to the controller. Don't send
an exit code, since the pretend job hasn't finished. Check that the
pretend output we sent ends up in the current build log.
WHEN worker manager calls POST /worker/bar/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "ikiwiki build output",
... "stderr": "",
... "exit-code": null
... }'
AND user calls GET /projects/foo/logs/current
THEN response has status 200, and text body "ikiwiki build output"
The current build step hasn't changed.
WHEN worker manager calls GET /worker/bar
THEN response has status 200,
... and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "ikiwiki --build"
... }"
Pretend current command finishes. Make sure current log updates, and
that we get a new thing to run.
WHEN worker manager calls POST /worker/bar/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "|more output",
... "stderr": "",
... "exit-code": 0
... }'
AND user calls GET /projects/foo/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/foo/logs/previous
THEN response has status 200,
... and text body "ikiwiki build output|more output"
WHEN worker manager calls GET /worker/bar
THEN response has status 200,
... and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "rsync"
... }"
Tell worker the rsync command also finishes. After that, there should
be nothing more to do. The current log should become empty, the
previous log will contain the previously current log.
WHEN worker manager calls POST /worker/bar/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "rsync output",
... "stderr": "",
... "exit-code": 0
... }'
WHEN user calls GET /projects/foo/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/foo/logs/previous
THEN response has status 200, and text body "rsync output"
WHEN user calls GET /worker/bar
THEN response has status 200, and an empty body
And we're done.
FINALLY stop controller instance
Two builds, two workers
-----------------------------------------------------------------------------
This section runs two builds using two workers. The primary goal here
is to make sure each worker gets consecutive steps for its own build,
so that it runs all the steps in the same workspace.
We start with some setup, defining a git repo and an ick project and
starting the controller.
SCENARIO run two builds with two workers
GIVEN a git repo foo.git with file index.mdwn containing
... "hello, world\n"
AND a git repo bar.git with file index.mdwn containing
... "hello, bar\n"
AND a project foo, using foo.git, publishing to foo-web
AND a project bar, using bar.git, publishing to bar-web
AND a running controller instance
Ensure controller knows of both projects. The list of project names
should be sorted alphabetically.
WHEN user calls GET /projects
THEN response has status 200,
... and JSON body "{ "projects": [ "bar", "foo" ] }"
There is no job running now, so if the worker manager asks for work,
it gets nothing.
WHEN worker manager calls GET /worker/one
THEN response has status 200, and an empty body
Trigger new builds on both projects. There is now work to do.
WHEN git server calls GET /projects/foo/+trigger
THEN response has status 200
WHEN worker manager calls GET /worker/one
THEN response has status 200, and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "ikiwiki --build"
... }"
The second worker should still get nothing to do.
WHEN worker manager calls GET /worker/two
THEN response has status 200, and an empty body
Trigger the other project, and the second worker gets something to do.
WHEN git server calls GET /projects/bar/+trigger
THEN response has status 200
WHEN worker manager calls GET /worker/two
THEN response has status 200, and JSON body "{
... "project": "bar",
... "git": "bar.git",
... "shell": "ikiwiki --build"
... }"
Pretend the build step for the first project is running, and send
output to the controller. Don't send an exit code, since the pretend
step hasn't finished. Check that the pretend output we sent ends up in
the current build log.
WHEN worker manager calls POST /worker/one/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "ikiwiki build output",
... "stderr": "",
... "exit-code": null
... }'
AND user calls GET /projects/foo/logs/current
THEN response has status 200, and text body "ikiwiki build output"
The current build step hasn't changed.
WHEN worker manager calls GET /worker/one
THEN response has status 200,
... and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "ikiwiki --build"
... }"
Pretend the build step finishes. Make sure current log updates, and
that we get a new thing to run.
WHEN worker manager calls POST /worker/one/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "|more output",
... "stderr": "",
... "exit-code": 0
... }'
AND user calls GET /projects/foo/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/foo/logs/previous
THEN response has status 200,
... and text body "ikiwiki build output|more output"
WHEN worker manager calls GET /worker/one
THEN response has status 200,
... and JSON body "{
... "project": "foo",
... "git": "foo.git",
... "shell": "rsync"
... }"
The other worker is still running its step, and if it asks, it gets
the same build step to run.
WHEN worker manager calls GET /worker/two
THEN response has status 200, and JSON body "{
... "project": "bar",
... "git": "bar.git",
... "shell": "ikiwiki --build"
... }"
Tell controller the rsync command of the first project also finishes.
After that, there should be nothing more to do. The current log should
become empty, the previous log will contain the previously current
log.
WHEN worker manager calls POST /worker/one/snippet,
... with JSON body '{
... "project": "foo",
... "stdout": "rsync output",
... "stderr": "",
... "exit-code": 0
... }'
WHEN user calls GET /projects/foo/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/foo/logs/previous
THEN response has status 200, and text body "rsync output"
WHEN user calls GET /worker/one
THEN response has status 200, and an empty body
Finish the other project build.
WHEN worker manager calls POST /worker/two/snippet,
... with JSON body '{
... "project": "bar",
... "stdout": "ikiwiki output",
... "stderr": "",
... "exit-code": 0
... }'
AND user calls GET /projects/bar/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/bar/logs/previous
THEN response has status 200,
... and text body "ikiwiki output"
WHEN worker manager calls GET /worker/two
THEN response has status 200,
... and JSON body "{
... "project": "bar",
... "git": "bar.git",
... "shell": "rsync"
... }"
WHEN worker manager calls POST /worker/two/snippet,
... with JSON body '{
... "project": "bar",
... "stdout": "second worker rsync output",
... "stderr": "",
... "exit-code": 0
... }'
WHEN user calls GET /projects/bar/logs/current
THEN response has status 200, and an empty body
WHEN user calls GET /projects/bar/logs/previous
THEN response has status 200, and text body
... "second worker rsync output"
WHEN user calls GET /worker/two
THEN response has status 200, and an empty body
And we're done.
FINALLY stop controller instance
|
