summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSytse Sijbrandij <sytse@gitlab.com>2015-07-23 15:00:35 +0000
committerKamil Trzcinski <ayufan@ayufan.eu>2015-07-24 15:08:00 +0200
commit4e6c975ada85ede86d76f5ca5d26bdf9c278873f (patch)
treeb740c5f4ee82c6bd0f8c32f9756d8093672148db /doc
parentff5812c7d4ed5f844ff9ccb5ecd0a4d22f38bd21 (diff)
downloadgitlab-ci-4e6c975ada85ede86d76f5ca5d26bdf9c278873f.tar.gz
Detail that people can use script to do `rake rspec` but also to call a `tests.sh`
Diffstat (limited to 'doc')
-rw-r--r--doc/yaml/README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/yaml/README.md b/doc/yaml/README.md
index 67e5ac1..a47c678 100644
--- a/doc/yaml/README.md
+++ b/doc/yaml/README.md
@@ -14,7 +14,8 @@ job2:
```
The above example is the simplest possible CI configuration with two separate jobs,
-where each of the jobs executes a different script.
+where each of the jobs executes a different commands.
+Of course a commands can execute code directly (`./configure;make;make install`) or run to a script (`test.sh`) in the respository.
Jobs are used to create builds, which are then picked up by [runners](../runners/README.md) and executed within the environment of the runner.
What is important, is that each job is run independently from each other.
@@ -179,4 +180,4 @@ Each instance of GitLab CI has an embedded debug tool called Lint.
You can find the link to the Lint in the project's settings page or use short url `/lint`.
## Skipping builds
-There is one more way to skip all builds, if your commit message contains tag [ci skip]. In this case, commit will be created but builds will be skipped
+There is one more way to skip all builds, if your commit message contains tag [ci skip]. In this case, commit will be created but builds will be skipped \ No newline at end of file