Yes. Docker plugin isn't able to separate the build environment from the
Jenkins slave though. The images used are more traditional slaves with
the jenkins slave daemon running inside the same container, which means
that the jenkins slave dependencies must be mixed with the build
environment.
Am 17.01.2018 um 20:57 schrieb Jacob Larsen:
> 1. Use Docker Slaves Plugin
>
> 2. Use Cloudbees Docker Custom build environment plugin
>
> 3. Use the Docker Pipeline plugin, specifically the .inside syntax
>
4. Use Docker plugin: Multiple Docker hosts, Container templates must be
defined either
There are 3 ways I know of that allows you to avoid having the Jenkins
slave dependency in the container:
1. Use Docker Slaves Plugin
- Has some limitations, but works for the most part. Supports
pipeline at least partially, and can run on dockerized slaves. Will not
run directly on
You can build your own docker image based in this
https://github.com/jenkinsci/docker-jnlp-slave but extending this one
https://hub.docker.com/_/oraclelinux/ , you only need to be sure that Java is
in it
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Hi ,
We have a problem on Jenkins on which container the job will run.
By default jenkins job is using jnlp container to run the Jobs.
inorder to run the jobs on the oraclelinux image.
1. We Successfully created docker-jnlp-slave image with oraclelinux image.
2. Able to pull docker-jnlp-slave
