From 1930ebcaadff66f919e8b69ee03e803f930f4ff7 Mon Sep 17 00:00:00 2001 From: Peter Thedens <pthedens@iastate.edu> Date: Sun, 15 Oct 2017 17:39:45 -0500 Subject: [PATCH] Update ci_faq.md --- documentation/ci_faq.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/ci_faq.md b/documentation/ci_faq.md index d083d62ef..a4112108b 100644 --- a/documentation/ci_faq.md +++ b/documentation/ci_faq.md @@ -36,10 +36,10 @@ directory. ## How does CI work? 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 -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, -`ci-build.sh` and `ci-test.sh`, which compile projects and run checks, -respectively. (Look at these scripts to learn more about how they work). If -some error occurs during the script (perhaps a forced error generated by a -failed test), then the runner sends a message back to Gitlab indicating that the -CI failed. Otherwise, it succeeds. +[`ci-build.sh`](ci/ci-build.sh) and [`ci-test.sh`](ci/ci-test.sh), +which compile projects and run checks, respectively. Look at these scripts to +learn more about how they work. If some error occurs during the script +(perhaps a forced error generated by a failed test), then the runner sends a +message back to Gitlab indicating that the CI failed. Otherwise, it succeeds. -- GitLab