2017-12-04 21:38 GMT+01:00 Jacob Larsen <[email protected]>:

> Here is a list of the options I know, but one important aspect to this is
> if you use pipeline or not in your builds as that affects your choices:
>
> Docker Custom Build Environment Plugin. This will use an existing executor
> to launch a container with the build. The images used need not be aware of
> Jenkins or dependencies. When I looked at it, it seemed abandoned, but it
> looks like someone is trying to pick it up again. It will probably take
> some time before it is up to date with new docker and Jenkins features.
> E.g. last I checked, pipeline was not supported. Also, it only works from
> physical Jenkins nodes.
>
pipeline is not supported by this plugin as the exact equivalent (even code
is a re-implementation) is docker-pipeline's "inside".


> Docker Slaves Plugin. This will provision slave containers on the fly from
> a single Docker host. Images need not be aware of Jenkins or dependencies.
> Limit on containers launched did not work for pipeline jobs last I checked.
> Also, this only works on a single Docker host.
>
docker-slaves-plugin do NOT require image to be aware of Jenkins or
dependencies, you can use arbitrary docker image, even without a JDK. This
was one initial goal of this plugin.

Docker Pipeline Plugin https://plugins.jenkins.io/docker-workflow. I just
> learned about this one from the previous message, but looking at the
> adoption rate, this must be the mainstream option. Odds are this would be
> your best bet to start, provided you are using pipeline.
>
> Using a build wrapper like SCUBA: https://github.com/
> JonathonReinhart/scuba in a shell step. This has the benefit of enabling
> manual/development builds to use the same steps as the automated Jenkins
> builds. For that particular wrapper, it does not support running from
> inside a container and creating sibling containers. I am considering a PR
> for that, but I think there are other wrappers that might support something
> like this.
>
> There are plugins that dynamically provision slaves from images and run
> builds on those. The common drawback for these would be that the images
> themselves must support running a jenkins Slave, e.g. have a Java runtime
> of a certain version installed.
>
> /Jacob
>
> On 2017-12-04 17:37, Jeeva Chelladhurai wrote:
>
> I would like to run my builds inside docker, so that I can manage
> different run times like node, python, go thru docker images.
>
> - Jeeva
>
> On Mon, Dec 4, 2017 at 5:51 PM, nicolas de loof <[email protected]>
> wrote:
>
>> (another) plugin of mines.
>> Same design as docker-pipeline's "docker.inside"
>>
>> Can you please describe your use-case so we give better advise ?
>>
>> if you just want to "build Docker images" as your initial message told,
>> then just run "docker build" within your job, what else ?
>>
>> 2017-12-04 13:15 GMT+01:00 Jeeva Chelladhurai <[email protected]>:
>>
>>> Any  thoughts on https://wiki.jenkins.io/displa
>>> y/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin
>>>
>>> On Mon, Dec 4, 2017 at 12:04 PM, Jeeva Chelladhurai <[email protected]>
>>> wrote:
>>>
>>>>
>>>>
>>>>> I have not tried this, so, cannot vouch for this. Please be cautious
>>>>> about the approach presented in this blog.
>>>>>
>>>>> http://niels.nu/blog/2017/continuous-blog-delivery-p2.html : you
>>>>> might be interested in Docker-in-Docker.
>>>>>
>>>>>
>>>>> Thanks for the suggestion.. Docker-in-Docker is been discouraged here
>>>> is good read on it https://jpetazzo.github.io/
>>>> 2015/09/03/do-not-use-docker-in-docker-for-ci/
>>>>
>>>> - Jeeva
>>>>
>>>
>>>
>>>
>>> --
>>> Jeeva K S Chelladhurai
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz
>>> 9w88K6af0QA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz9w88K6af0QA%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/ms
>> gid/jenkinsci-users/CANMVJznKg%3DXKpeaT62PVkmEvLh4kruCyc1HV%
>> 2BQGFNtnjLhX%3DLQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJznKg%3DXKpeaT62PVkmEvLh4kruCyc1HV%2BQGFNtnjLhX%3DLQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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/CAK5CbZVoig-s%3DvfVi5SEcrLVjBwZ5-0danHP-X54_
> CogRT9n0Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZVoig-s%3DvfVi5SEcrLVjBwZ5-0danHP-X54_CogRT9n0Q%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/189e04a2-be8d-1052-bb05-cebd482ffc72%40larsen.net
> <https://groups.google.com/d/msgid/jenkinsci-users/189e04a2-be8d-1052-bb05-cebd482ffc72%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/CANMVJzn7U2NvWGsYrWggNK_-Kc_zM9hE6AYh56BT-c3SHb5Wzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to