Does docker-slaves-plugin with pipeline assume Linux?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Does docker-slaves-plugin with pipeline assume Linux?

Geoff Bache

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

slide
The extra slash after "agent" is odd, I assume that the docker create command is generated by the plugin?

On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <[hidden email]> wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVchoy-gy%3Dfkp0S932qKeF3K4f_AY8SCHAESTe%3DSnfr3YA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Geoff Bache

Yes, I didn't contribute anything to that generated command.

On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
The extra slash after "agent" is odd, I assume that the docker create command is generated by the plugin?

On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mI53pD4ACAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">geoff...@...> wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mI53pD4ACAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dca1ccde-53bb-4056-ba43-68456da927d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

nicolas de loof-2
I'm on vacation so can't help before 1 week. Pipeline is fully supported, please check global configuration for the agent image you have configured for docker-slaves-plugin

Le 10 août 2017 5:30 PM, "Geoff Bache" <[hidden email]> a écrit :

Yes, I didn't contribute anything to that generated command.

On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
The extra slash after "agent" is odd, I assume that the docker create command is generated by the plugin?

On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <[hidden email]> wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dca1ccde-53bb-4056-ba43-68456da927d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm_ia4FF7oxQipYuWwTR%2BOGBUchcrm6yy80%2Bd7Zna2DJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Jacob Larsen-2

Looks like the agent image is the default one that was just set in the latest release, see https://github.com/jenkinsci/docker-slaves-plugin/commit/2d0470b27a84ddff00c3e1adc7aec9b7e8dece00

Take a look at the Docker Slaves section of the global Jenkins configuration. The remoting image is probably set to jenkins/agent/. Notice the final slash as Slide mentions, I believe the specific error you experience would go away by removing that final slash.

Anyhow, that would probably not work for you no matter what. Since you are using a Windows Docker instance then you will need Windows images for the remoting image and the SCM image. But I have no idea if the volume mounts would work there. You might be right that this part is hardcoded to Linux.

/Jacob


On 2017-08-10 18:19, nicolas de loof wrote:
I'm on vacation so can't help before 1 week. Pipeline is fully supported, please check global configuration for the agent image you have configured for docker-slaves-plugin

Le 10 août 2017 5:30 PM, "Geoff Bache" <[hidden email]> a écrit :

Yes, I didn't contribute anything to that generated command.

On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
The extra slash after "agent" is odd, I assume that the docker create command is generated by the plugin?

On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <[hidden email]> wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dca1ccde-53bb-4056-ba43-68456da927d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm_ia4FF7oxQipYuWwTR%2BOGBUchcrm6yy80%2Bd7Zna2DJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e57f2fcc-af2f-f59e-4844-3654e19e94d8%40larsen.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

nicolas de loof-2
Oh yes that's a stupid typo in default value, will fix this and push a release. We are still missing multi arch docker images so this same id can pull a Windows version of the agent image

Le 10 août 2017 8:51 PM, "Jacob Larsen" <[hidden email]> a écrit :

Looks like the agent image is the default one that was just set in the latest release, see https://github.com/jenkinsci/docker-slaves-plugin/commit/2d0470b27a84ddff00c3e1adc7aec9b7e8dece00

Take a look at the Docker Slaves section of the global Jenkins configuration. The remoting image is probably set to jenkins/agent/. Notice the final slash as Slide mentions, I believe the specific error you experience would go away by removing that final slash.

Anyhow, that would probably not work for you no matter what. Since you are using a Windows Docker instance then you will need Windows images for the remoting image and the SCM image. But I have no idea if the volume mounts would work there. You might be right that this part is hardcoded to Linux.

/Jacob


On 2017-08-10 18:19, nicolas de loof wrote:
I'm on vacation so can't help before 1 week. Pipeline is fully supported, please check global configuration for the agent image you have configured for docker-slaves-plugin

Le 10 août 2017 5:30 PM, "Geoff Bache" <[hidden email]> a écrit :

Yes, I didn't contribute anything to that generated command.

On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
The extra slash after "agent" is odd, I assume that the docker create command is generated by the plugin?

On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <[hidden email]> wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dca1ccde-53bb-4056-ba43-68456da927d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm_ia4FF7oxQipYuWwTR%2BOGBUchcrm6yy80%2Bd7Zna2DJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e57f2fcc-af2f-f59e-4844-3654e19e94d8%40larsen.net.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmZBpY7%3DnsXnx2V13zr%2B%3Dtw61Kc6XhoFBmrEefHNj1yfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Geoff Bache
In reply to this post by Geoff Bache

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

nicolas de loof-2
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <[hidden email]> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3DwdajHjV-JR1DZiowpx-O9jWYHTt-e1zRdyrgguY2jwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Geoff Bache

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description?

On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="iBjRIOYzCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">geoff...@...> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="iBjRIOYzCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41050b00-f6f2-4f56-9607-a1e8e8aadb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Thiago Carvalho Davila
That is very sad.. I have slaves for windows and linux, and I was begining a migration of my machine slaves to containers =(

Is there a JIRA feature created for that cause?

Em 11/08/2017 04:52:49, Geoff Bache escreveu:

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description?

On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <geoff...@...> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@....
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41050b00-f6f2-4f56-9607-a1e8e8aadb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c027f377da0189d5277bdd934f925defc5e61f25%40serpro.gov.br.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

nicolas de loof-2
I think you just miss a Jenkins agent docker image for Windows architecture, everything else should work (linux style paths aren't an issue afaik)

Le 11 août 2017 16:37, "Thiago Carvalho Davila" <[hidden email]> a écrit :
That is very sad.. I have slaves for windows and linux, and I was begining a migration of my machine slaves to containers =(

Is there a JIRA feature created for that cause?

Em 11/08/2017 04:52:49, Geoff Bache escreveu:

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description?

On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <[hidden email]> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41050b00-f6f2-4f56-9607-a1e8e8aadb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c027f377da0189d5277bdd934f925defc5e61f25%40serpro.gov.br.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3DeRyhZTX4%2BJzHrZZFq-T6ZttXhSXa%2Bke5MFgWbnJVu_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

Jacob Larsen-2

Wouldn't you need a Windows SCM image as well?


On 2017-08-12 18:56, nicolas de loof wrote:
I think you just miss a Jenkins agent docker image for Windows architecture, everything else should work (linux style paths aren't an issue afaik)

Le 11 août 2017 16:37, "Thiago Carvalho Davila" <[hidden email]> a écrit :
That is very sad.. I have slaves for windows and linux, and I was begining a migration of my machine slaves to containers =(

Is there a JIRA feature created for that cause?

Em 11/08/2017 04:52:49, Geoff Bache escreveu:

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description?

On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <[hidden email]> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41050b00-f6f2-4f56-9607-a1e8e8aadb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c027f377da0189d5277bdd934f925defc5e61f25%40serpro.gov.br.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3DeRyhZTX4%2BJzHrZZFq-T6ZttXhSXa%2Bke5MFgWbnJVu_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/649b7a6b-9c45-99a8-0b2f-e4185545585c%40larsen.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does docker-slaves-plugin with pipeline assume Linux?

nicolas de loof-2
Yes indeed. But as long g as you use git this one is actually ran in Jenkins agent container due to an implementation issue.

Le 13 août 2017 12:16 PM, "Jacob Larsen" <[hidden email]> a écrit :

Wouldn't you need a Windows SCM image as well?


On 2017-08-12 18:56, nicolas de loof wrote:
I think you just miss a Jenkins agent docker image for Windows architecture, everything else should work (linux style paths aren't an issue afaik)

Le 11 août 2017 16:37, "Thiago Carvalho Davila" <[hidden email]> a écrit :
That is very sad.. I have slaves for windows and linux, and I was begining a migration of my machine slaves to containers =(

Is there a JIRA feature created for that cause?

Em 11/08/2017 04:52:49, Geoff Bache escreveu:

OK, I think we can conclude from my evidence that it doesn't yet work on Windows then: I'm not trying to do anything beyond basic usage. Perhaps you could write this in the plugin description?

On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
This plugin has never been tested for Windows containers, so I can't tell if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache" <[hidden email]> a écrit :

I removed the extra slash in global configuration, but it still fails and there are still Linux-style paths that I don't seem to be able to configure. See text below.
I also tried using jenkinsci/slave, which the tooltip recommends, but got the same error.

/Geoff

Start Docker container to host the build
$ docker volume create
$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/ jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/": invalid volume specification: '20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'

On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:

Hi all,

 

I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to get it to use docker containers instead of building locally. The docker-slaves-plugin looked like the most convenient interface for this among a confusing forest of different Docker plugins.

 

So I installed it and pointed it at my Docker image in the configuration. It carried on exactly as before and ignored Docker entirely, even after Jenkins restart.

 

I then found a hint that I should replace “node” with “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the following in my build log (with debug option enabled).

Note the “docker create” line which seems to be referring to a bunch of linux paths that just don’t exist and looks a bit hardcoded...


If, as I suspect, this isn't supported, any hints on which plugin to use instead would be appreciated.

 

Regards,

Geoff Bache

 

Start Docker container to host the build

$ docker volume create

$ docker create --interactive --log-driver=none --env TMPDIR=/home/jenkins/.tmp --user 10000:10000 --rm --volume 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/ jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar /home/jenkins/slave.jar

Error parsing reference: "jenkins/agent/" is not a valid repository/tag: invalid reference format

[Pipeline] // dockerNode

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.io.IOException: Failed to create docker image

        at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemotingContainer(CliDockerDriver.java:176)

        at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemotingContainer(DefaultDockerProvisioner.java:88)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:58)

        at it.dockins.dockerslaves.DockerComputerLauncher.launch(DockerComputerLauncher.java:49)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:123)

Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException

        at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(OneShotSlave.java:145)

        at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSlave.java:129)

        at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneShotSlave.java:154)

        at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSlave.java:96)

        at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$PlaceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)

        at hudson.model.ResourceController.execute(ResourceController.java:97)

        at hudson.model.Executor.run(Executor.java:405)

Finished: FAILURE

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ce34aee-8be4-4065-b189-4f27c079e781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41050b00-f6f2-4f56-9607-a1e8e8aadb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c027f377da0189d5277bdd934f925defc5e61f25%40serpro.gov.br.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3DeRyhZTX4%2BJzHrZZFq-T6ZttXhSXa%2Bke5MFgWbnJVu_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/649b7a6b-9c45-99a8-0b2f-e4185545585c%40larsen.net.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3Deq23yRU1k-6TMs_s2FnYy2HRN9COeWPLi5mLbWOMJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...