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
|
<!--
Copyright 2017-2018 Lars Wirzenius
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
# Build step fails
This scenario tests the controller API to simulate a build, when one
build step fails.
SCENARIO build step fails
Set up the controller.
GIVEN an RSA key pair for token signing
AND controller config uses statedir at the state directory
AND controller config uses https://blobs.example.com as blob service
AND an access token for user with scopes
... uapi_pipelines_post
... uapi_projects_post
... uapi_projects_id_pipelines_id_put
... uapi_projects_id_pipelines_id_get
... uapi_projects_id_builds_get
... uapi_workers_id_get
... uapi_builds_get
... uapi_builds_id_get
... uapi_logs_id_get
AND a running ick controller
Add up a project and its pipelines.
WHEN user makes request POST /pipelines with a valid token and body
... {
... "pipeline": "construct",
... "actions": [
... { "shell": "day 1" },
... { "shell": "day 2" }
... ]
... }
THEN result has status code 201
WHEN user makes request POST /projects with a valid token and body
... {
... "project": "rome",
... "pipelines": ["construct"]
... }
THEN result has status code 201
Register a worker.
GIVEN an access token for worker-manager with scopes
... uapi_workers_post
... uapi_work_post
... uapi_work_id_get
WHEN worker-manager makes request POST /workers with a valid token and body
... {
... "worker": "obelix"
... }
THEN result has status code 201
Trigger build. First with an invalid status, then a real one.
WHEN user makes request PUT /projects/rome/pipelines/construct
... with a valid token and body { "status": "triggered" }
THEN result has status code 200
Worker wants work and gets the first step to run.
WHEN worker-manager makes request GET /work/obelix
THEN result has status code 200
AND body matches
... {
... "build_id": "rome/1",
... "log": "/logs/rome/1",
... "worker": "obelix",
... "project": "rome",
... "pipeline": "construct",
... "parameters": {},
... "step": {
... "action": "create_workspace"
... }
... }
Worker reports some build output. Note the exit code indicating
failure.
WHEN worker-manager makes request POST /work with a valid token and body
... {
... "build_id": "rome/1",
... "worker": "obelix",
... "project": "rome",
... "pipeline": "construct",
... "exit_code": 1,
... "stdout": "",
... "stderr": "eek!",
... "timestamp": "2017-10-27T17:08:49"
... }
THEN result has status code 201
A build step failed, so now the build has ended, and there's no more
work to do.
WHEN worker-manager makes request GET /work/obelix
THEN result has status code 200
AND body matches {}
User sees changed status.
WHEN user makes request GET /workers/obelix
THEN result has status code 200
AND body matches
... {
... "worker": "obelix",
... "doing": {}
... }
The pipeline status indicates it's idle.
WHEN user makes request GET /projects/rome/pipelines/construct
THEN result has status code 200
AND body matches { "status": "idle" }
Also, there's a build with a log.
WHEN user makes request GET /builds
THEN result has status code 200
AND body matches
... {
... "builds": [
... {
... "build_id": "rome/1",
... "build_number": 1,
... "log": "/logs/rome/1",
... "worker": "obelix",
... "project": "rome",
... "pipeline": "construct",
... "actions": [
... { "action": "create_workspace" },
... { "shell": "day 1" },
... { "shell": "day 2" }
... ],
... "current_action": null,
... "parameters": {},
... "status": 1
... }
... ]
... }
WHEN user makes request GET /builds/rome/1
THEN result has status code 200
AND body matches
... {
... "build_id": "rome/1",
... "build_number": 1,
... "log": "/logs/rome/1",
... "worker": "obelix",
... "project": "rome",
... "pipeline": "construct",
... "actions": [
... { "action": "create_workspace" },
... { "shell": "day 1" },
... { "shell": "day 2" }
... ],
... "current_action": null,
... "parameters": {},
... "status": 1
... }
WHEN user makes request GET /logs/rome/1
THEN result has status code 200
AND result has header Content-Type: text/plain
AND body text is "eek!"
FINALLY stop ick controller
|
