You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/gitlab/setup.md
+13-13
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,14 @@
4
4
5
5
Using `scm-engine` as a webhook server allows for richer feature set compared to [GitLab CI pipeline](#gitlab-ci-pipeline) mode
6
6
7
-
-`+` Reacting to comments
8
-
-`+` Access to webhook event data in scripts via `webhook_event.*` (see [server docs](../commands/server.md) for more information)
9
-
-`+` A single `scm-engine` instance (and single token) for your GitLab project, group, or instance depending on where you configure the webhook.
10
-
-`+` Each Project still have their own `.scm-engine.yml` file, it's downloaded via the API when the server is processing a webhook event.
11
-
-`+` A single "bot" identity across your projects.
12
-
-`+` Turn key once configured; if a project want to use `scm-engine` they just need to create the `.scm-engine.yml` file in their project.
13
-
-`+` Real-time reactions to changes
14
-
-`-`No intuitive access to [`evaluation` logs](../commands/evaluate.md) within GitLab (you can see them in the server logs or in the webhook failure log)
7
+
-[X] Real-time reactions to changes.
8
+
-[X] Reacting to comments.
9
+
-[X] Access to webhook event data in scripts via `webhook_event.*` (see [server docs](../commands/server.md) for more information).
10
+
-[X] A single `scm-engine` instance (and single token) for your GitLab project, group, or instance depending on where you configure the webhook.
11
+
-[X] Each Project still have their own `.scm-engine.yml` file, it's downloaded via the API when the server is processing a webhook event.
12
+
-[X] A single "bot" identity across your projects.
13
+
-[X] Turn key once configured; if a project want to use `scm-engine` they just need to create the `.scm-engine.yml` file in their project.
14
+
-[ ]No intuitive access to [`evaluation` logs](../commands/evaluate.md) within GitLab (you can see them in the server logs or in the webhook failure log).
15
15
16
16
**Setup**:
17
17
@@ -22,11 +22,11 @@ Using `scm-engine` as a webhook server allows for richer feature set compared to
22
22
23
23
Using `scm-engine` within a GitLab CI pipeline is straight forward - every time a CI pipeline runs, `scm-engine` will [evaluate](../commands/evaluate.md) the Merge Request.
24
24
25
-
-`+` Simple & quick installation.
26
-
-`+` Limited access token permissions.
27
-
-`+` Easy access to [`evaluation` logs](../commands/evaluate.md) within the GitLab CI job.
28
-
-`-` Can't react to comments; only works within a CI pipeline.
29
-
-`-` Higher latency for reacting to changes depending on how fast CI jobs run (and where in the pipeline it runs).
25
+
-[X] Simple & quick installation.
26
+
-[X] Limited access token permissions.
27
+
-[X] Easy access to [`evaluation` logs](../commands/evaluate.md) within the GitLab CI job.
28
+
-[ ] Can't react to comments; only works within a CI pipeline.
29
+
-[ ] Higher latency for reacting to changes depending on how fast CI jobs run (and where in the pipeline it runs).
0 commit comments