Using Docker Custom Build Environment Plugin approach with Pipeline is already implemented as docker-pipeline plugin. What we'd like to investigate during GSoC is to get further, considering limitations of the existing approach, and a docker-centric way to manage build elasticity and customization.
2016-03-16 14:38 GMT+01:00 <[email protected]>: > I got it. Therefore, does it mean that I can integrate the notion of > "pipeline as code" with the base of the Docker Custom Build Environment > Plugin, so that we can run the pipeline steps in the container by using > plein Docker CLI? > > > > Le mardi 15 mars 2016 18:10:24 UTC+1, nicolas de loof a écrit : >> >> docker-pipeline does rely on docker-exec to enter a container an run >> commands inside it, so the jenkins slave remoting still applies to the >> hosting node. >> this was inspired by Docker Custom Build Environment Plugin (aka Oki >> Docki plugin) >> >> Main benefit is you can run arbitrary docker image, you don't need one >> created to host a jenkins slave. Typically, you can use an image you use on >> your own developer workstation to reproduce a specific build environment. >> >> But this setup also has some limitations, one of them being you need a >> local docker daemon on jenkins slave, as it relies on bind mounting project >> workspace >> >> >> >> 2016-03-15 16:58 GMT+01:00 <[email protected]>: >> >>> Hello, everyone! >>> >>> I'm working on the subject about the "Integration of Docker plugins with >>> Jenkins 2.0 features". I have learned that the Docker-Pipeline Plugin can >>> run the pipeline steps inside the containers by using Jenkins Slave, but >>> i'm wondering the interest of running the pipeline steps by depending on >>> the Docker CLI instead of the Jenkins Slave remoting in the images? >>> >>> Thanks, >>> Guobao >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" 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-dev/486afcb3-7a38-45e9-823b-74710dd6e041%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/486afcb3-7a38-45e9-823b-74710dd6e041%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 Developers" 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-dev/a3f065e1-5a60-4a35-a4b2-7202d8f17913%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a3f065e1-5a60-4a35-a4b2-7202d8f17913%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 Developers" 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-dev/CANMVJznMCR48SXNPn2e1JnN0QDXmr4Dq0fjCvsC1nBmB5vYhcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
