Re: The official docker image jenkins/jenkins:lts is missing ruby

We recommend to NOT run build within the master image anyway, and always connect a slave computer/container to enforce resources isolation. Le 27 juil. 2017 9:12 PM, "Jacob Larsen" a écrit : > I agree. Extending the base image is the way to go. Alternatively, you can > use a

Re: The official docker image jenkins/jenkins:lts is missing ruby

+1 IMHO even if it's required maintenance, it would be a good idea to create and maintain your own image and store it on an internal repository for many reasons (lower coupling between your builds and the parent image, build reproducibility, better performance, and so on). 2017-07-27 21:12

Re: The official docker image jenkins/jenkins:lts is missing ruby

I agree. Extending the base image is the way to go. Alternatively, you can use a clean image for the master and set up slaves with ruby, labeled appropriately. /Jacob On 2017-07-27 16:02, Mark Waite wrote: I would be very surprised if the Jenkins docker image were extended to include ruby.

Re: The official docker image jenkins/jenkins:lts is missing ruby

I would be very surprised if the Jenkins docker image were extended to include ruby. Ruby is not a mandatory requirement for Jenkins development and adding it to the base Jenkins Docker image will increase the size of the docker image for all Jenkins users. Mark Waite On Thu, Jul 27, 2017 at

The official docker image jenkins/jenkins:lts is missing ruby

Dear list, I'm setting up a software development lifecycle infrastructure. I decided to use the official docker container provided by Jenkins community and the idea is not to extend it writing my own image avoiding the amount of work required to maintain an image and to keep as standard as