Global before_ and after_ script defined by admin

Description

To setup CI environment inside of a Docker container we need to run few .sh scripts. We add to each of our .gitlab-ci.yml: before_script and after_script that always looks the same. Maybe we could introduce global script definitions? Maybe in config.toml or somewhere else? It would be very useful to setup and tear down environment before tasks that regular developer can achieve inside .gitlab-ci.yml.

Proposal

Add global before_script and after_script. Maybe inside config.toml or elsewhere inside /etc/gitlab-runner.

Have you seen pre_build_script in https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section? I think it is the thing, you're looking for. There is no post_build_script, but I think we could think about adding it :)

How possibly I missed it? :3 Thank you @tmaczukin for pointing this out!

post_build_script would be extremely useful too. In our case – we're creating metadata file on remote with informations about commit that triggered the build, project ID etc. This would fit perfectly in our case to have post_build_script.

I agree that such option could be useful. And by default it would be not used, so it wouldn't be a problem for users, who don't want to use it.

Let's make a feature proposal from this :)

added ~1009246 feature proposal labels

changed milestone to %Backlog

mentioned in merge request !460 (merged)

closed via merge request !460 (merged)