[JIRA] [docker-slaves-plugin] (JENKINS-30600) git isn't ran inside build container

[nicolas.deloof@gmail.com (JIRA)]

Nicolas De Loof created an issue

Jenkins / JENKINS-30600 git isn't ran inside build container Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin, git-client-plugin Created: 22/Sep/15 10:25 PM Priority: Minor Reporter: Nicolas De Loof Using docker-slaves, the checkout build phase is ran with commands inside the remoting container (which by change has git) not inside the configured build container. This is due to git-client to create it's own LocalLauncher vs using the Node's one. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[nicolas.deloof@gmail.com (JIRA)]

Nicolas De Loof commented on JENKINS-30600

Re: git isn't ran inside build container git-client plugin do not rely on Launcher/FilePath abstraction but sends the whole GitClient implementation class to remote, making it just impossible to rely on a Launcher from caller. Would need to fully refactor GitClient implementation to run on master.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[nicolas.deloof@gmail.com (JIRA)]

Nicolas De Loof commented on JENKINS-30600

Re: git isn't ran inside build container

see https://github.com/jenkinsci/git-client-plugin/pull/211

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-30600

git isn't ran inside build container

Change By: Jesse Glick Component/s: docker-slaves-plugin

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-30600 git isn't ran inside build container

Change By: Jesse Glick Labels: docker-slaves

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick started work on JENKINS-30600

Change By: Jesse Glick Status: Open In Progress

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-30600

Re: git isn't ran inside build container Affects docker-workflow as well from what I can tell: if Jenkins is configured with only a CLI Git tool (the default), and an agent lacks a Git executable, docker.image('cloudbees/java-build-tools').inside {git '…'} will fail on the git command with an error indicating that the command was not found—because it is being run in the agent’s namespace, not the container’s.

Add Comment