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

[Federico Paolantoni]

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

[Mark Waite]

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

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/29e93174-df1e-4d7f-a36c-e47780fc7d77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jacob Larsen]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEsoZw5kcnrv750wFn6BbOWO5_8vH5ZcDOsHmc9B-7usg%40mail.gmail.com.

[Michael Pailloncy]

+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 GMT+02:00 Jacob Larsen <ja...@larsen.net>:

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 <federico....@gmail.com> 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 jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/29e93174-df1e-4d7f-a36c-e47780fc7d77%40googlegroups.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEsoZw5kcnrv750wFn6BbOWO5_8vH5ZcDOsHmc9B-7usg%40mail.gmail.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e61bcd3c-6ef6-f141-d92f-5321f6bf74fe%40larsen.net.

[nicolas de loof]

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" <ja...@larsen.net> 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 <federico....@gmail.com> 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 jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/29e93174-df1e-4d7f-a36c-e47780fc7d77%40googlegroups.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEsoZw5kcnrv750wFn6BbOWO5_8vH5ZcDOsHmc9B-7usg%40mail.gmail.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e61bcd3c-6ef6-f141-d92f-5321f6bf74fe%40larsen.net.