@@ -200,9 +200,10 @@ The above specification will make sure that `job` is built by a runner that have
### when
`when` is used to implement jobs that are run in case of failure or despite the failure.
The `when` can be set to one of the following values:
1.`on_success` - execute build only when all builds from prior stages succeeded. This is default.
1.`on_failure` - execute build only when at least one of the build from prior stages failed.
`when` can be set to one of the following values:
1.`on_success` - execute build only when all builds from prior stages succeeded. This is the default.
1.`on_failure` - execute build only when at least one build from prior stages failed.
1.`always` - execute build despite the status of builds from prior stages.
```
...
...
@@ -250,4 +251,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
\ No newline at end of file
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
