[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave

[aherit...@apache.org (JIRA)]

Title: Message Title

Arnaud Héritier commented on JENKINS-32861   Re: Checking Dockerfile in project doesn't work with Slave It seems that it doesn't work in all cases. --file option of docker build must be an absolute path Otherwise you have this error : Build Docker image from ./spring-petclinic//Dockerfile ... $ docker build --file Dockerfile /Users/arnaud/CloudBees/Support/cases/33463/3-cloudbees-support_2016-02-16_15.20.59_UsineValidation/jenkins-home/jobs/zd-33463/workspace/spring-petclinic unable to prepare context: The Dockerfile (/Users/arnaud/CloudBees/Support/cases/33463/3-cloudbees-support_2016-02-16_15.20.59_UsineValidation/Dockerfile) must be within the build context (/Users/arnaud/CloudBees/Support/cases/33463/3-cloudbees-support_2016-02-16_15.20.59_UsineValidation/jenkins-home/jobs/zd-33463/workspace/spring-petclinic) FATAL: Failed to build docker image from project Dockerfile The message is misleading because it says that /Users/arnaud/CloudBees/Support/cases/33463/3-cloudbees-support_2016-02-16_15.20.59_UsineValidation/Dockerfile isn't under /Users/arnaud/CloudBees/Support/cases/33463/3-cloudbees-support_2016-02-16_15.20.59_UsineValidation/jenkins-home/jobs/zd-33463/workspace/spring-petclinic but in docker command line we have --file Dockerfile. --file must be an absolute path. Here is the PR: https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/43 Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.