diff options
author | Stefan Agner <stefan@agner.ch> | 2019-02-16 22:52:10 +0300 |
---|---|---|
committer | Stefan Agner <stefan@agner.ch> | 2019-02-16 22:52:10 +0300 |
commit | 1fbbdb48943b785478e117c964427be2d5bccf49 (patch) | |
tree | 7d2c61a4b94cede1489bcb14b600f99429df0d91 /doc | |
parent | 28aa4d331c67fd3206858f57a30a3c14449216f3 (diff) |
clarify after_script cwd situation in README.md
Diffstat (limited to 'doc')
-rw-r--r-- | doc/ci/yaml/README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index 8c8a31e9323..31f99cd5e68 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -96,9 +96,9 @@ This can be an array or a multi-line string. jobs, including failed ones. This has to be an array or a multi-line string. The `before_script` and the main `script` are concatenated and run in a single context/container. -The `after_script` is run separately, so depending on the executor, changes done -outside of the working tree might not be visible, e.g. software installed in the -`before_script`. +The `after_script` is run separately. The current working directory is set back to +default. Depending on the executor, changes done outside of the working tree might +not be visible, e.g. software installed in the `before_script`. It's possible to overwrite the globally defined `before_script` and `after_script` if you set it per-job: |