Add support to configure Initial Image from global configuration #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @jonhermansen,
Recently Docker announced download rate limit on anonymous docker image downloads and
docker-custom-build-environment
plugin internally uses analpine 3.6
call it an initial image/initImage (hard coded inside plugin). This image is downloaded for most job runs.Here is a PR to make this image configurable in
Jenkins Global Configuration
under a new sectionBuild In Docker Configuration
. This will enable/support configuring the image from local repositories instead of pointing it to docker hub.Change log:
Build In Docker Configuration
in global configuration.Init Image
to allow the Initial image used by the plugin to be configurable (global.jelly).initImage
toalpine:3.6
.Preview of the changes:
Configuration preview:
Note: Value defaults to
alpine:3.6
Form validation:
~ Prasad.