<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Hi, </div><div class="gmail_quote"><br></div><div class="gmail_quote"> Vaclav presented the build pipeline very nicely and this would take out lot of tension for building the code, checking the code standards and test cases from the developer.</div><div class="gmail_quote"><br></div><div class="gmail_quote">I would like to add few points on this.</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Tue, Feb 9, 2016 at 8:08 PM, Vaclav Pavlin <<a href="mailto:vpavlin@redhat.com">vpavlin@redhat.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><h1 style="color:rgb(0,0,0);font-family:'Times New Roman'"><span style="white-space:pre-wrap;font-family:arial,sans-serif;font-size:small;font-weight:normal">Hi all,</span></h1><pre style="white-space:pre-wrap;color:rgb(0,0,0)">As KB wrote, I brought up the idea of using OpenShift as a glue (i.e.
workflow controller). The result can be found here:
<a href="https://github.com/vpavlin/cccp-demo-openshift" style="color:rgb(0,75,145)">https://github.com/vpavlin/cccp-demo-openshift</a>
TL;DR:
The repository contains OpenShift Template defining the workflow - build,test, delivery and (very poorly) implements the steps through Docker images (i.e. Dockerfiles and run scripts).
</pre></blockquote><div>The developer should do only git push to his VCS and this should trigger the build process in the pipeline. </div><div><br></div><div>In this TDD process all the environments (including the build, test, delivery) would be created as a container and once the step is over it will destroy the environment. As output this will generate a application runtime along with the successfully built application code to registry. </div><div><br></div><div>As you mentioned this would be tagged with test along with jenkins build id, so that developer or QA can trace for which commit this is built.</div><div><br></div><div>Then for the next stages, successfully built image would be deployed to openshift instance to get through the test, delivery stages checking, along with the quality gates.</div><div><br></div><div>all the stages should be linked to pipeline and should be easily re-producible so that any one can check or regenerate the issues instantly. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><pre style="white-space:pre-wrap;color:rgb(0,0,0)">It's easily runnable in Vagrant with use of Project Atomic Developer Bundle.
If you are interested in more info, I'd suggest to read the readme in the repo, I hope it summarizes it clearly.
It's a very minimal demo, but I think it suggests the path, which could take us to the Unicorns land, quite well:).
Let me know in case of any questions, suggestions or requests for guidance in case anybody decides to take this further.</pre></blockquote><div>I would like to take this further, please let me know if my thought process is in the same line as yours or any changes, suggestions.</div><div><br></div><div>Few weeks back I created almost a similar system (without vagrant) and it was very much welcomed by the developers.</div><div><br></div><div>Thanks </div><div>Bamacharan </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><pre style="white-space:pre-wrap;color:rgb(0,0,0)">
Cheers,
Vašek
</pre><div><br></div>
> On Sun, Feb 7, 2016 at 3:22 AM, Karanbir Singh <<a href="mailto:kbsingh@centos.org">kbsingh@centos.org</a>> wrote:<br>
> hi,<br>
><br>
> Yesterday a few of us met for a face to face walk through of the CentOS<br>
> Container Pipeline we've been talking about. The aim was to rescope the<br>
> upstream projects we can lean on, share code with, and help - and then<br>
> find the glue pieces that could bring this code base together.<br>
><br>
> The larger picture effectively boils down to :<br>
> - Find the components needed to track code git repos ( either in<br>
> <a href="http://git.centos.org" rel="noreferrer" target="_blank">git.centos.org</a> or elsewhere )<br>
> - Find the components needed to now build that code, containerise the<br>
> code, push it through a test process, and then deliver the containers<br>
> either locally into a centos transitional container registry, or to a<br>
> CDN like wider centos registry or if the user so desires, to a third<br>
> part registry ( provided a good process can be find to handle the<br>
> credentials needed ).<br>
> - We'd want to use this pipeline both internally, for the CentOS Linux<br>
> components ( eg. a LAMP container from CentOS Linux 7 ), for SIG<br>
> components via cbs output ( eg. SCLo SIG folks shipping containers for<br>
> their content ), as well as open this up via a trivial UI, for anyone in<br>
> the community who'd like to come and consume this pipeline.<br>
><br>
> the key piece that we didnt have clarity on was the orchestration and<br>
> glue that could bind the various software components. Vaclav Pavlin,<br>
> brought up that we might be able to use openshift templates in order to<br>
> get the job runs done - if the input for the templates could be derived<br>
> from the cccp-index, either via the jjb work already done, or writing a<br>
> new filter into JJB, we might be able to execute a fairly scaleable<br>
> solution without needing to own any piece of the over all code.<br>
><br>
> Additionally, there is a fair interest from the Fedora team ( ie Adam! )<br>
> working on the same problem in their space, mostly consuming the<br>
> identical code stack, within and for their infra, their constraints and<br>
> aims.<br>
><br>
> Over the coming days we are going to try and work though PoC's, get some<br>
> infra setup and trial running through some of the user stories we want<br>
> to execute on.<br>
><br>
> Finally, a quick shout out to everyone for coming together at pretty<br>
> much the last minute adhoc meeting - Fabian Arrotin, Brian Stinson,<br>
> Christoph Goern, Vaclav Pavlin, Aaron Weitekamp, Tomas Tomecek, Adam<br>
> Miller, Dusty Mabe, Honza Horak, Radek Vokal as well as Tim Waugh, Bama<br>
> Charan and Mohammed Zeeshan for dialing into the meeting.<br>
><br>
> And to everyone else, want to build containers with us ? come talk to us<br>
> - we'd love to make sure we include as many user stories to get great<br>
> scope before we start implementing bits.<br>
><br>
> regards<br>
><br>
><br><pre style="white-space:pre-wrap;color:rgb(0,0,0)">><i> --
</i>><i> Karanbir Singh, Project Lead, The CentOS Project
</i>><i> +44-207-0999389 | <a href="http://www.centos.org/" style="color:rgb(0,75,145)">http://www.centos.org/</a> | <a href="http://twitter.com/CentOS">twitter.com/CentOS</a>
</i>><i> GnuPG Key : <a href="http://www.karan.org/publickey.asc" style="color:rgb(0,75,145)">http://www.karan.org/publickey.asc</a>
</i>><i> _______________________________________________
</i>><i> CentOS-devel mailing list
</i>><i> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" style="color:rgb(0,75,145)">CentOS-devel at centos.org</a>
</i>><i> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" style="color:rgb(0,75,145)">https://lists.centos.org/mailman/listinfo/centos-devel</a>
</i>></pre></blockquote></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Bamacharan Kundu<br>IRC Nick- bamachrn<br><br></div>
</div></div>