[JIRA] (JENKINS-58297) Declarative Pipeline with docker can't retry when pull image failed.

[giser_wkfor@163.com (JIRA)]

daniel zhang created an issue

Jenkins / JENKINS-58297 Declarative Pipeline with docker can't retry when pull image failed. Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-07-02 09:10 Environment: jenkins: 2.164.3 Pipeline Model Definition Plugin : 1.3.3 Priority: Minor Reporter: daniel zhang we need an option configure like 'alwaysPull' that can support retry when pull image failed due to some unexpected situations. Also we can configure with retry in the option block, but I don't like that. [Pipeline] stage[Pipeline] { (Declarative: Agent Setup)[Pipeline] sh+ docker pull fw-registry-aws-dev.ss.aws.fwmrm.net/adserving/ads-build-ci:latest Error response from daemon: received unexpected HTTP status: 503 Service Unavailable Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[giser_wkfor@163.com (JIRA)]

daniel zhang updated an issue

Jenkins / JENKINS-58297 Declarative Pipeline with docker can't retry when pull image failed.

Change By: daniel zhang

we need an option configure like 'alwaysPull' that can support retry when pull image failed due to some unexpected situations. Also we can configure with retry in the option block, but I don't like that.

[Pipeline] stage[Pipeline] { (Declarative: Agent Setup)[Pipeline] sh+ docker pull fw-registry-aws-dev.ss.aws.fwmrm.net/adserving/ads-build-ci:latest xxx

Error response from daemon: received unexpected HTTP status: 503 Service Unavailable

Add Comment

[giser_wkfor@163.com (JIRA)]

daniel zhang closed an issue as Duplicate

Jenkins / JENKINS-58297 Declarative Pipeline with docker can't retry when pull image failed.

Change By: daniel zhang Status: Open Closed Assignee: Andrew Bayer daniel zhang Resolution: Duplicate

Add Comment