Developers can define settings in specific build configurations within their
projects, such as
configuring a proxy
for Git cloning. Rather than requiring developers to define certain settings in
each of their build configurations, cluster administrators can use admission
control plug-ins to configure global build defaults and overrides that
automatically use these settings in any build.
The settings from these plug-ins are not set in the build configurations or
builds themselves, but rather are only used during the build process. This
allows administrators to change the global configuration at any time, and any
builds that are re-run from existing build configurations or builds will get the
BuildDefaults admission control plug-in allows administrators to set
global defaults for settings such as the Git HTTP and HTTPS proxy, as well as
default environment variables. These defaults do not overwrite values that have
been configured for a specific build. However, if those values are not present
on the build definition, they are set to the default value.
BuildOverrides admission control plug-in allows administrators to
override a setting in a build, regardless of the value stored in the build. It
currently supports overriding the
forcePull flag on a build strategy to
enforce always refreshing the local image during a build by pulling the image
from the registry. This ensures that a user can only build with an image that
they are allowed to pull.