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" <[email protected]> a écrit :

> 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.  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 3:33 AM Federico Paolantoni <
> [email protected]> wrote:
>
>> 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
>> possible.
>> But:
>> I noticed that ruby is not provided with the container, so i wonder if
>> the community is considering to add it on the official supported image,
>> considering that there is no way to inject ruby, rake an gems inside the
>> builds as done for nodejs,
>>
>> Thank you
>>
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/29e93174-df1e-4d7f-a36c-
>> e47780fc7d77%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/29e93174-df1e-4d7f-a36c-e47780fc7d77%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAO49JtEsoZw5kcnrv750wFn6BbOWO
> 5_8vH5ZcDOsHmc9B-7usg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEsoZw5kcnrv750wFn6BbOWO5_8vH5ZcDOsHmc9B-7usg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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 [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/e61bcd3c-6ef6-f141-d92f-5321f6bf74fe%40larsen.net
> <https://groups.google.com/d/msgid/jenkinsci-users/e61bcd3c-6ef6-f141-d92f-5321f6bf74fe%40larsen.net?utm_medium=email&utm_source=footer>
> .
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJznn9XHFnfQAVnw%2BVJpYUcjYg%2B5Zy01SpGq-wCdEP%2BNKog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to