Skip to content
Snippets Groups Projects
Commit 1930ebca authored by Peter Thedens's avatar Peter Thedens
Browse files

Update ci_faq.md

parent 51b59528
No related branches found
No related tags found
No related merge requests found
...@@ -36,10 +36,10 @@ directory. ...@@ -36,10 +36,10 @@ directory.
## How does CI work? ## How does CI work?
When a commit is added to a branch in our repository, a notification is sent out When a commit is added to a branch in our repository, a notification is sent out
to our gitlab-ci-runner, which instructs it to checkout the updated branch and to our gitlab-ci-runner, which instructs it to checkout the updated branch and
run the directive in `.gitlab-ci.yml`. It then runs each directive, which is run the directive in [`.gitlab-ci.yml`](.gitlab-ci.yml). It then runs each directive, which is
made up of bash scripts to execute. In our case, we run two scripts, made up of bash scripts to execute. In our case, we run two scripts,
`ci-build.sh` and `ci-test.sh`, which compile projects and run checks, [`ci-build.sh`](ci/ci-build.sh) and [`ci-test.sh`](ci/ci-test.sh),
respectively. (Look at these scripts to learn more about how they work). If which compile projects and run checks, respectively. Look at these scripts to
some error occurs during the script (perhaps a forced error generated by a learn more about how they work. If some error occurs during the script
failed test), then the runner sends a message back to Gitlab indicating that the (perhaps a forced error generated by a failed test), then the runner sends a
CI failed. Otherwise, it succeeds. message back to Gitlab indicating that the CI failed. Otherwise, it succeeds.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment