forked from fedora-ci/ciboard
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathPageHelp.tsx
More file actions
283 lines (279 loc) · 10.2 KB
/
PageHelp.tsx
File metadata and controls
283 lines (279 loc) · 10.2 KB
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
/*
* This file is part of ciboard
* Copyright (c) 2021, 2023 Andrei Stepanov <astepano@redhat.com>
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser 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
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public License
* along with this program; if not, write to the Free Software Foundation,
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
*/
import {
Text,
PageSection,
TextContent,
CodeBlockCode,
} from '@patternfly/react-core';
import { config } from '../config';
import { PageCommon } from './PageCommon';
import { ExternalLink } from './ExternalLink';
const Help = () => (
<TextContent>
<Text component="h1">Welcome to CI Dashboard!</Text>
<Text component="p">
CI Dashboard displays details of testing events, which happened for
the supported artifacts. As the source of information it uses the{' '}
</Text>
<ExternalLink href="https://pagure.io/fedora-ci/messages">
Factory 2.0 CI UMB messages
</ExternalLink>{' '}
consumed from the Unified Message Bus (UMB). Currently it makes it
possible to discover testing events only.
<h2>Supported artifacts</h2>
The dashboard currently supports these artifacts
<ul>
<li>
Brew rpm builds - builds from the{' '}
<ExternalLink href="https://brewweb.engineering.redhat.com">
Brew build system
</ExternalLink>
</li>
<li>
Koji rpm builds - builds from the{' '}
<ExternalLink href="https://koji.fedoraproject.org/koji">
Koji build system
</ExternalLink>
</li>
<li>
Copr builds - build from the{' '}
<ExternalLink href="https://copr.devel.redhat.com">
internal Copr build system
</ExternalLink>{' '}
or{' '}
<ExternalLink href="https://copr.fedorainfracloud.org">
Fedora Copr build system
</ExternalLink>
</li>
<li>
Red Hat modules - build from{' '}
<ExternalLink href="http://mbsweb.engineering.redhat.com">
Module Build Service
</ExternalLink>
</li>
<li>
Productmd composes - build from{' '}
<ExternalLink href="http://mbsweb.engineering.redhat.com">
Module Build Service
</ExternalLink>
</li>
</ul>
<h2>Search</h2>
<h3>Via menu</h3>
<p>
The dashboard provides a simple interface for searching. Currently
you can search only by artifact name. The name is dependent on the
type of the artifact.
</p>
<p>
For Brew/Koji rpm builds and Red Hat modules the search value is the
component name. For Copr builds the artifact name consists from the
repository name plus the package, e.g. @ksh/latest/ksh.
</p>
<h3>Via URL</h3>
<p>The dashboard provides advanced search via URL:</p>
<p className="padding-left-20">
{window.location.origin}
/#/artifact/ARTIFACT_NAME/FIELD/VALUE[,VALUE,...]?FIELD=VALUE
{'&'}
FIELD=VALUE
{'&'}
...
</p>
<h4>Examples</h4>
<p>
Search all artifacts of build issuers plautrba and lvrabec,
non-scratch only
</p>
<p className="padding-left-20">
<ExternalLink
href={`${window.location.origin}/#/artifact/brew-build/issuer/plautrba,lvrabec?scratch=false`}
>
{window.location.origin}
/#/artifact/brew-build/issuer/plautrba,lvrabec?scratch=false
</ExternalLink>
</p>
<p>Search events for modules with name httpd, nginx and llvm-toolset</p>
<p className="padding-left-20">
<ExternalLink
href={`${window.location.origin}/#/artifact/redhat-module/name/httpd,nginx,llvm-toolset`}
>
{window.location.origin}
/#/artifact/redhat-module/name/httpd,nginx,llvm-toolset
</ExternalLink>
</p>
<h4>Possible values for ARTIFACT_NAME</h4>
<ul>
<li>brew-build</li>
<li>copr-build</li>
<li>koji-build</li>
<li>redhat-module</li>
</ul>
<h4>Possible fields and values</h4>
<table style={{ width: '100%' }}>
<tbody>
<tr>
<th>Field</th>
<th>Value</th>
</tr>
<tr>
<td>aid</td>
<td>
An integer. Specifies the artifact ID. Dependent on
artifact type:
<ul>
<li>brew-build, koji build - task ID</li>
<li>redhat-module - module build ID</li>
</ul>
</td>
</tr>
<tr>
<td>component</td>
<td>
Name of the component, applicable for artifacts
brew-build, koji-build and copr-build.
</td>
</tr>
<tr>
<td>name</td>
<td>
Name of the module, applicable for artifact
redhat-module only.
</td>
</tr>
<tr>
<td>nvr</td>
<td>
NVR of the rpm build, applicable for artifact brew-build
and koji-build.
</td>
</tr>
<tr>
<td>nsvc</td>
<td>
NSVC of the module build, applicable for artifact
redhat-module.
</td>
</tr>
<tr>
<td>owner</td>
<td>
Name of the owner of the artifact, usually who built it.
</td>
</tr>
<tr>
<td>scratch</td>
<td>
Boolean - true or false. Applicable only for brew build
and koji-build.
</td>
</tr>
</tbody>
</table>
<h3>Via GraphQL</h3>
<p>
You can construct GraphQL queries and execute them on the
dashboard's backend GraphQL server. The GraphQL backend is usually
located at:
</p>
<p className="padding-left-20">
{window.location.origin}
/graphql
</p>
<h4> Disclaimers</h4>
<p>
Note: the API is not officially supported and its primary use is for
the CI Dashboard front-end. It is not guaranteed to be stable and it
can change arbitrarily without prior notice.
</p>
<h4>Examples</h4>
<p>
To retrieve build tags by NVR, your query could look something like
this:
</p>
<p className="padding-left-20">
<CodeBlockCode id="code-content">
{`query brew {
koji_build_tags_by_nvr(nvr: $NVR, instance: rh|fp|cs|pn){
arches
id
locked
name
perm
perm_id}
}`}
</CodeBlockCode>
</p>
<h2>Onboarding</h2>
<p>
To onboard your system to the dashboard, just start sending out
messages in the Factory 2.0 CI UMB messages format to the specified
virtual topic namespace. In case of any questions, see Contacts.
</p>
<h2>Development / Contribution</h2>
<p>
Dashboard is built using React.js, Patternfly and other JS goodies.
</p>
<p>
The project is currently developed on github. Contributions are
always welcome.
</p>
<table style={{ width: '45%' }}>
<tbody>
<tr>
<td>Fontend:</td>
<td>
<ExternalLink href="https://github.com/fedora-ci/ciboard/">
https://github.com/fedora-ci/ciboard/
</ExternalLink>
</td>
</tr>
<tr>
<td>Backend:</td>
<td>
<ExternalLink href="https://github.com/fedora-ci/ciboard-server/">
https://github.com/fedora-ci/ciboard-server/
</ExternalLink>
</td>
</tr>
<tr>
<td>Kai:</td>
<td>
<ExternalLink href="https://github.com/fedora-ci/kaijs/">
https://github.com/fedora-ci/kaijs/
</ExternalLink>
</td>
</tr>
</tbody>
</table>
<h2>Contacts</h2>
<p>IRC: #osci or #baseosci</p>
<p>Mailing list: osci-list@redhat.com baseos-ci@redhat.com</p>
</TextContent>
);
export function PageHelp() {
return (
<PageCommon title={`Help | ${config.defaultTitle}`}>
<PageSection isFilled>
<Help />
</PageSection>
</PageCommon>
);
}