From 4e6c975ada85ede86d76f5ca5d26bdf9c278873f Mon Sep 17 00:00:00 2001 From: Sytse Sijbrandij Date: Thu, 23 Jul 2015 15:00:35 +0000 Subject: Detail that people can use script to do `rake rspec` but also to call a `tests.sh` --- doc/yaml/README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc') 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 -- cgit v1.2.1