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
|
<!--
Copyright 2017-2019 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/>.
-->
# Controller pipeline management
The Ick2 controller manages information about named pipelines.
Pipelines are sequences of steps to achieve part of a project build.
They're described like resources like this:
EXAMPLE pipeline resource
{
"pipeline": "build-website",
"parameters": {
"foo": "bar"
},
"actions": [
{
"shell": "git clone git://git.liw.fi/ick2-website src",
"where": "host"
},
{
"shell": "cd src && ikiwiki --setup ikiwiki.setup",
"where": "host"
},
{
"shell": "cd html && rsync -a --delete . server::/srv/http/ick2/.",
"where": "host"
}
]
}
In other words, there are several things that define a pipeline:
* The `name`. This is used for referreing to the pipeline in the API.
* A set of parameters, which are currently ignored.
* A sequence of actions. At the moment, each action is a shell
command to be run, but that will change later.
## Managing pipelines
First we test the controller API for managing pipelines, without
running them. We start by starting an instance of the controller.
SCENARIO managing pipelines
GIVEN an access token for user with scopes
... uapi_pipelines_get
... uapi_pipelines_post
... uapi_pipelines_id_get
... uapi_pipelines_id_put
... uapi_pipelines_id_delete
AND a running ick controller
WHEN user makes request GET /pipelines
THEN result has status code 200
AND body matches { "pipelines": [] }
WHEN user makes request POST /pipelines with a valid token and body
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "git clone git://repo src" },
... { "where": "host", "shell": "mkdir html" },
... { "where": "host", "shell": "ikiwiki src html" }
... ]
... }
THEN result has status code 201
AND body matches
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "git clone git://repo src" },
... { "where": "host", "shell": "mkdir html" },
... { "where": "host", "shell": "ikiwiki src html" }
... ]
... }
Creating a new pipeline with the same name is forbidden.
WHEN user makes request POST /pipelines with a valid token and body
... {
... "pipeline": "foo/build_website"
... }
THEN result has status code 409
WHEN user makes request GET /pipelines
THEN result has status code 200
AND body matches
... {
... "pipelines": [
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "git clone git://repo src" },
... { "where": "host", "shell": "mkdir html" },
... { "where": "host", "shell": "ikiwiki src html" }
... ]
... }
... ]
... }
WHEN user stops ick controller
GIVEN a running ick controller
WHEN user makes request GET /pipelines/foo/build_website
THEN result has status code 200
AND body matches
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "git clone git://repo src" },
... { "where": "host", "shell": "mkdir html" },
... { "where": "host", "shell": "ikiwiki src html" }
... ]
... }
WHEN user makes request PUT /pipelines/build_websitte with a valid token
... and body
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "build-it" }
... ]
... }
THEN result has status code 200
AND body matches
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "build-it" }
... ]
... }
WHEN user makes request GET /pipelines/foo/build_website
THEN result has status code 200
AND body matches
... {
... "pipeline": "foo/build_website",
... "actions": [
... { "where": "host", "shell": "build-it" }
... ]
... }
WHEN user makes request DELETE /pipelines/foo/build_website
THEN result has status code 200
WHEN user makes request GET /pipelines/foo/build_website
THEN result has status code 404
WHEN user makes request PUT /pipelines/doesnotexist with a valid token and body
... {
... "pipeline": "doesnotexist"
... }
THEN result has status code 404
FINALLY stop ick controller
|
