<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 31, 2016 at 10:27 AM, James Strachan <span dir="ltr"><<a href="mailto:jstracha@redhat.com" target="_blank">jstracha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">I’m a huge fan of 2); but currently that requires a pod for the JNLP slave and another pod for the docker image; which on premise or on Dedicated doesn’t really matter. But on OpenShift Online that is gonna be painful (3 pods just for builds!); so option 1) using one or two curated pools of slaves of custom pod/mages might be simpler for Online. e.g. one slave pool for maven/java and one for nodejs?</div></blockquote><div><br><div class="gmail_default" style="font-family:georgia,serif">yeah so i've been leaning towards (1) due to it needing fewer pods, but it does mean we have to provide some slave images, and/or an easy way to create new slave images (which we actually already have here:<br><a href="https://github.com/openshift/origin/blob/master/examples/jenkins/master-slave/jenkins-slave-template.json">https://github.com/openshift/origin/blob/master/examples/jenkins/master-slave/jenkins-slave-template.json</a>), so certainly (2) feels like a better long term solution.<br><br></div><div class="gmail_default" style="font-family:georgia,serif">Providing maven/java and nodejs slave images out of the box seems likely.<br></div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div><div><div class="h5"><br><div><blockquote type="cite"><div>On 31 May 2016, at 15:19, Tomas Nozicka <<a href="mailto:tnozicka@redhat.com" target="_blank">tnozicka@redhat.com</a>> wrote:</div><br><div><div>Hi,<br><br>how do we want to run our Jenkins "build slaves" in our pipelines?<br><br>Options:<br>1) kubernetes plugin [1]<br>= Example =<br>node ('java8-maven') {<br> sh 'mvn package'<br>}<br>= EOF =<br> - tightly coupled to Jenkins instance (requires predefined pools of<br>slaves which you can choose from)<br> - build environment is defined by admin not pipeline (Jenkinsfile)<br> - not generic<br><br>2) kubernetes-workflow plugin [2]<br>= Example =<br>kubernetes.pod('buildpod').withImage('java8-maven').inside{<br> sh 'mvn package'<br>}<br>= EOF =<br> + loosely coupled to Jenkins instance<br> + pipeline (Jenkinsfile) specifies build environment<br> + generic (pipelines can specify custom images)<br><br>I am for option 2 because of the loose coupling to Jenkins and ability<br>to specify (custom) build images as part of Jenkinsfile.<br><br>And AFAIK catapult project is partially about taking user pipelines and<br>setting those up with OpenShift(+Jenkins), I just don't see it working<br>with the tight coupling and option 1.<br><br>If we decide to go with option 2 we should probably integrate<br>kubernetes-workflow plugin into jenkins-1-centos7:dev image.<br><br>What do you think?<br><br>Thanks,<br>Tomas<br><br>[1] - <a href="https://wiki.jenkins-ci.org/display/JENKINS/Kubernetes+Plugin" target="_blank">https://wiki.jenkins-ci.org/display/JENKINS/Kubernetes+Plugin</a><br>[2] - <a href="https://github.com/fabric8io/kubernetes-workflow" target="_blank">https://github.com/fabric8io/kubernetes-workflow</a><br><br>_______________________________________________<br>kontinuity-dev-public mailing list<br><a href="mailto:kontinuity-dev-public@redhat.com" target="_blank">kontinuity-dev-public@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/kontinuity-dev-public" target="_blank">https://www.redhat.com/mailman/listinfo/kontinuity-dev-public</a><br></div></div></blockquote></div><br></div></div><div> <div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px"><br>James</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">-------</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">Red Hat</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px"><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">Twitter: @jstrachan</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">Email: <a href="mailto:jstracha@redhat.com" target="_blank">jstracha@redhat.com</a></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">Blog: <a href="https://medium.com/@jstrachan/" target="_blank">https://medium.com/@jstrachan/</a></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px"><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">fabric8: <a href="http://fabric8.io/" target="_blank">http://fabric8.io/</a></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px">open source microservices platform</div> </div> <br></div></div><br>_______________________________________________<br> kontinuity-dev-public mailing list<br> <a href="mailto:kontinuity-dev-public@redhat.com">kontinuity-dev-public@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/kontinuity-dev-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/kontinuity-dev-public</a><br> <br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Ben Parees | OpenShift<br><br></div></div> </div></div>