diff options
| author | Sytse Sijbrandij <sytse@gitlab.com> | 2015-07-23 15:00:35 +0000 |
|---|---|---|
| committer | Sytse Sijbrandij <sytse@gitlab.com> | 2015-07-23 15:00:35 +0000 |
| commit | 85b09ca232c664c02188ad1ab2e62fa9540bad9b (patch) | |
| tree | dbd265f469da3e87bfa64474840fd674a35b9ec7 | |
| parent | 8a629882ca84572f13c83f7dadd0d6248263bafb (diff) | |
| download | gitlab-ci-detail-two-possibilities-for-scripts.tar.gz | |
Detail that people can use script to do `rake rspec` but also to call a `tests.sh`detail-two-possibilities-for-scripts
| -rw-r--r-- | doc/yaml/README.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/yaml/README.md b/doc/yaml/README.md index 6600988..988d1ab 100644 --- a/doc/yaml/README.md +++ b/doc/yaml/README.md @@ -13,7 +13,8 @@ job2: ``` The above example is the simplest possible CI configuration with two separate jobs, -where each of the job executes different script. +where each of the jobs executes a different bash command. +Of course a bash command can execute code directly (`./configure;make;make install`) or run to a bash script (`test.sh`) in the respository. Jobs are used to create builds, which are then picked by [runners](../runners/README.md) and executed within environment of the runner. What is important that each job is run independently from each other. @@ -177,4 +178,4 @@ Each instance of GitLab CI has an embedded debug tool 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 |