So that only the upper layer is used as docker image for Jenkins and the actual build&test commands from Jenkinsfile are used (instead of the commands from Dockerfile).
A fix for this issue was just released in Docker Pipeline plugin version 1.19. From the release notes:
Deprecate the dockerFingerprintFrom and dockerFingerprintRun steps and stop calling them during docker.build and image.run. Fixes various issues with Dockerfile parsing and parsing arguments to docker build.
Hi, I have docker pipeline plugin version 1.19 running and still have the same issue. Is it really resolved? Or am I doing something wrong here.
[Bitbucket] Build result notified
11:02:05 java.io.IOException: Cannot retrieve .Id from 'docker inspect nginx:stable-alpine as prod'
11:02:05 at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:220)
11:02:05 at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:118)
11:02:05 at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:88)
11:02:05 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
11:02:05 at hudson.security.ACL.impersonate(ACL.java:290)
11:02:05 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
11:02:05 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
11:02:05 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11:02:05 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
11:02:05 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
11:02:05 at java.lang.Thread.run(Thread.java:748)
11:02:05 Finished: FAILURE