diff options
| author | Tomasz Maczukin <tomasz@maczukin.pl> | 2019-06-11 23:31:44 +0200 |
|---|---|---|
| committer | Tomasz Maczukin <tomasz@maczukin.pl> | 2019-06-12 08:44:17 +0200 |
| commit | f4b5f930ff7252468c69cf4decbbb05d44ba3b71 (patch) | |
| tree | 25facd3466acfa641ffc427b6b633f701b10bae9 /qa | |
| parent | 9bf141cf718ab9ca770c3bd6b7e2c6719cbe9da7 (diff) | |
| download | gitlab-ce-docs/make-it-clear-about-after-script-context.tar.gz | |
Leave clear notices about after_script execution contextdocs/make-it-clear-about-after-script-context
We frequently see new issues mentioning that something defined
in `before_script` or `script` doesn't work with `after_script`.
Our documentation mentions that first two are concatenated and
executed together, why the third one is executed in a separated
shell context. But it looks like it's not clear enough.
Since this misunderstanding of how scripts are being executed
is repeated frequently, let's make it more clear in docs.
Diffstat (limited to 'qa')
0 files changed, 0 insertions, 0 deletions