Skip to content

Draft: Add PreStop hook from job response

What does this MR do?

This merge request add the possibility to define the pre_stop hook at the job description level. Its operation is equivalent to the hook defined in the runner's toml. The job definition overwrites the runner definition

Why was this MR needed?

preStop hook can only be set at the runner level. Now it can be overwrite at the job level to have more flexibility

What's the best way to test this MR?

For the moment it is just at the runner level so what I did is that I intercepted the job response with a software (Postman, Burp...) and add manually to the JSON the expected hook that doesn't exist yet on Gitlab side.

What are the relevant issue numbers?

Closes #27877

Edited by Baptiste Lalanne

Merge request reports