Starting with GitLab Runner 11.4 we added a base support for feature flags in GitLab Runner.
These flags may be used:
For beta features that we want to make available for volunteers but don’t want to enable publicly yet.
A user who wants to use such feature and accepts the risk, can enable it explicitly while the wide group of users will be unaffected by potential bugs and regressions.
For breaking changes that need a deprecation and removal after few releases.
While the product evolves some features may be removed or changed. Sometimes it may be even something that is generally considered as a bug, but users already managed to find some workarounds for it and a fix could affect their configurations.
In that cases the feature flag is used to switch from old behavior to the new wan on demand. Such fix such ensure that the old behavior is deprecated and marked for removal together with the feature flag that protects the new behavior.
At this moment feature flags mechanism is based on environment variables. To make the change hidden behind
the feature flag active a corresponding environment variable should be set to
1. To make the
change hidden behind the feature flag disabled a corresponding environment variable should be set to
|Feature flag||Default value||Deprecated||To be removed with||Description|
|✓||12.0||Enables the fix for entrypoint configuration when |
|✓||12.0||Enable the helper image to use the new commands when helper_image is specified. This will start using the new API that will be used in 12.0 and stop showing the warning message in the build log|
|✗||Disables EnableDelayedExpansion for error checking for when using Window Batch shell|
|✓||12.0||Disables the new strategy for |
|✓||12.3||Disables the new strategy for Docker executor to cache the content of |
|✓||12.6||Disables the new ordering of volumes mounting when |