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" a écrit :
> Wouldn't you need a Windows SCM image as well?
>
> On 2017-08-12 18:56, nicolas de loof wrote:
>
>
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"
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"
a écrit :
> That is very sad.. I have slaves for windows and linux, and
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
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
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 écrit :
>
> I removed the extra slash in global configuration, but it still fails and
> there are still Linux-style paths
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
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" a écrit :
> Looks like the agent image is the
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
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" a écrit :
>
> Yes, I didn't contribute anything to that
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
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 wrote:
> Hi all,
>
>
>
> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to
> get it to use docker
12 matches
Mail list logo