-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Environment:pipeline-model-definition-plugin v1.2
-
Similar Issues:
Version 1.2 of pipeline-model-definition-plugin changes the behavior of docker images. `docker pull` is now performed for docker images specified in `agent`. Previously this was not performed.
This change affects use cases where the docker image only exists locally. It will obviously fail if `docker pull` is called.
The change was introduced in https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/182
The simple workaround is to patch the plugin to revert this change, but it would be nice to avoid that.
Hopefully this could be reverted to old behavior or/and an option added for configuration.
- links to
I met same issue as Ryan Fitzsimon.
When I set 'alwaysPull false' within stage block, it works fine as expect to use local image. However, if the same config is set within the top 'pipeline/agent' block, it still always do 'docker pull' and the local image does not work.