[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29194) doesn't work with remote docker servers (also when Jenkins itself is containerized)

[jb-pub-jenk...@aviat.net (JIRA)]

Title: Message Title

Jean-Baptiste Aviat commented on JENKINS-29194   Re: doesn't work with remote docker servers (also when Jenkins itself is containerized) Great plugin! Therefore I hit the same issue there. In order for the plugin to equally work with remote containers, we would to follow something like that: send the workspace: $ tar -cf - /path/to/workspace | docker exec -i ef01 /bin/sh -c "mkdir -p /tmp/workspace && tar -C /tmp/workspace -xf -" for each build step, send and run the command: /tmp/hudson_abcd.sh: $ cat /tmp/hudson_abcd.sh | docker exec -i ef01 /bin/sh -c "cat > /tmp/build_step.sh && /tmp/build_step.sh" retrieve the built workspace to allow Jenkins to gather files (coverage...) and archive it: $ docker cp ef01:/tmp/workspace /path/to/archived/builds/ Pros: we don't need to share volumes anymore with the spawn container. Cons: we have the overhead of files copy. I don't know what's the plan for docker-compose integration, but I think the previous steps would work the same assuming we know the ID of the container we want use to run build steps. 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.