[JIRA] (JENKINS-32709) Docker Pipeline plugin: docker.withServer still executes on local Jenkins server

[sven.sch...@hmmh.de (JIRA)]

Title: Message Title

Sven Scheil edited a comment on JENKINS-32709   Re: Docker Pipeline plugin: docker.withServer still executes on local Jenkins server [~jglick] How do I achieve this: A declarative jenkinsfile spawns an agent-container on a remote docker host by only the name of the image. The container entrypoint starts the jnlp-agent and jenkins-master. When the jnlp-agent is up and running the communication between jenkins-master and agent is established. Now the jenkins-master tells the agent whats the next action defined in the jenkinsfile. The agents executes the build-steps and returns via jnlp the console log messages. This is the way we like to utilize the docker-plugin and declarative jenkinsfiles, but the jnlp-communication is not established. It's only established when we use predefined docker template. But we don't wann used the dockertemplates. Our development-teams should specify an image of their choice inside the jenkinsfile. What we need is a way to define the same information from the docker template configuration inside the jenkinsfile.   { { code:java} pipeline { }} {{ agent { }} {{ docker { }} {{ image 'cloudbees/java-with-docker-client' }} {{ } }} {{ } }}{{ stages { }} {{ stage('Example Build') { }} {{ steps { }} {{ echo 'Step1' }} {{ git changelog: false, credentialsId: 'SSH-Test', poll: false, url: 'ssh://git@X : / Y/Z /P .git' } } {{ } }} {{ } }}{{}}}   { { code:java } }} Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.