-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major
-
Component/s: pipeline-model-definition-plugin
-
Environment:jenkins 2.167
pipeline-model-definition 1.3.5
With the current version (1.3.5) of pipeline-model-definition a defined custom docker registry server is ignored. In version 1.3.4.1 this worked (so I rolled back to this version).
This is a snippet with version 1.3.4.1:
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/MyProject_1.0
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withDockerRegistry
[Pipeline] {
[Pipeline] sh
+ docker inspect -f . my-build:latest
Error: No such object: my-build:latest
[Pipeline] sh
+ docker inspect -f . 192.168.17.28:5000/my-build:latest
Error: No such object: 192.168.17.28:5000/my-build:latest
[Pipeline] sh
+ docker pull 192.168.17.28:5000/my-build:latest
latest: Pulling from my-build
This is a snippet of version 1.3.5: (missing "withDockerRegistry")
[Pipeline] Start of Pipeline [Pipeline] node Running on Jenkins in /var/jenkins_home/workspace/MyProject_1.0 [Pipeline] { [Pipeline] sh + docker inspect -f . my-build:latest Error: No such object: my-build:latest [Pipeline] sh + docker pull my-build:latest Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
If you need any further information, please tell.
- duplicates
-
-
- In Review
-
