You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to use CI as a build argument, it must be explicitly declared with an ARG directive in the Dockerfile:
ARG CI
Desired Behavior:
For example, allow CI=true to be passed automatically when specified via --opt=build-arg:CI=true without requiring the explicit ARG declaration, similar to how http_proxy, https_proxy, etc. are handled.
Rationale:
CI=true is a common convention across CI engines. Development tools and utilities may adjust their behavior when detecting they're running in a CI environment. And most Dockerfile's RUN commands execute those dev tools.
Having the ability to set CI=true available in the environment without requiring an explicit ARG declaration would streamline configurations and ensure/enforce consistent behavior
Currently, to use CI as a build argument, it must be explicitly declared with an ARG directive in the Dockerfile:
ARG CI
Desired Behavior:
For example, allow
CI=true
to be passed automatically when specified via--opt=build-arg:CI=true
without requiring the explicitARG
declaration, similar to how http_proxy, https_proxy, etc. are handled.Rationale:
CI=true is a common convention across CI engines. Development tools and utilities may adjust their behavior when detecting they're running in a CI environment. And most Dockerfile's RUN commands execute those dev tools.
Having the ability to set CI=true available in the environment without requiring an explicit ARG declaration would streamline configurations and ensure/enforce consistent behavior
Refs:
The text was updated successfully, but these errors were encountered: