Skip to content

Add variables to disable jobs

Raphaël Hertzog requested to merge hertzog/pipeline:disable-job-variables into master

The syntax to disable jobs is too complicated. I propose to make every job conditional to some DISABLE_* variables that can be easily overridden. In the same logic, the use of diffoscope should be controlled by a variable, without requiring a full job override.

Remain the question of how to handle jobs that should be disabled by default. We could use an ENABLE_FOO variable set to 0 by default that the user must override to 1. If we later want to enable that job by default, we can switch to DISABLE_FOO but keep compatibility with ENABLE_FOO:

only:
  variables:
    - $DISABLE_FOO == "0" && ($ENABLE_FOO == "" || $ENABLE_FOO == "1")

Maybe we should use "yes/no" or "true/false", let me know if you have a clear preference.

Merge request reports