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
|
Building a project
=============================================================================
This chapter 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
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
|
