On 26 February 2018 at 15:29, Christian Gagneraud wrote:
> On 26 February 2018 at 03:10, nicolas de loof
> wrote:
>> docker support in declarative pipeline relies on docker-workfow plugin,
>> which require the jenkins slave to have access to a LOCAL docker daemon,
>> which means the docker agent
On 26 February 2018 at 03:10, nicolas de loof wrote:
> docker support in declarative pipeline relies on docker-workfow plugin,
> which require the jenkins slave to have access to a LOCAL docker daemon,
> which means the docker agent you are provisioning on computer B using docker
> plugin HAS to b
Hi
Has somebody use this plugin into a Jenkinsfile (Scriptting type).
I just need it to make it work after an execption has happen but do not know
how to put it on the Jenkisfile.
Thanks
Jo
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
docker support in declarative pipeline relies on docker-workfow plugin,
which require the jenkins slave to have access to a LOCAL docker daemon,
which means the docker agent you are provisioning on computer B using
docker plugin HAS to be configured with /var/run/docker.sock (so, the one
from B) bi
Hi there,
I have a machine A that runs Jenkins and Bitbucket-server in docker containers.
I have a machine B, that just has docker listening over tcp.
I have a project that uses Declarative pipeline with "agent { docker
'foobar:X.Y'}"
I'm using "jenkinsci/blueocean:latest" docker image with
"docke