<div dir="ltr">Hey, any progress here? <div><br></div><div>Vašek</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 10, 2016 at 4:19 PM, Vaclav Pavlin <span dir="ltr"><<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Feb 10, 2016 at 3:33 PM, Bamacharan Kundu <span dir="ltr"><<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a>></span> wrote:<br><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"><div dir="ltr">Hi Vaclav,<br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Feb 10, 2016 at 6:53 PM, Vaclav Pavlin <span dir="ltr"><<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>></span> wrote:<br><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"><div dir="ltr"><div>Hi Bamacharan,</div><div><br></div>I'd be careful with per commit builds in case of build from Dockerfile as it takes time and resources (presumably a lot of both) because we have to build in clean env and with --no-cache.</div></blockquote><div><br></div></span><div>Why don't we take a layered based aproach, we can take the base image from local system then build it, this will save lot of time? I saw multiple dockerfiles for build,test,delivery which are intern the same image only.</div></div></div></div></blockquote><div><br></div></span><div>To un-confuse people who didn't see our IRC convo - the Dockerfiles in cccp-demo-openshift repo represent containers which implement individual steps of the workflow - not the images/containers which are tested and delivered.</div><div><br></div><div>To answer "Why don't we take a layered based aproach": We do, building from Dockerfile follows the layered approach. The problem I am trying to emphasize is that we need clean environment for every build, otherwise we could introduce inconsistency again..But I think this could be easily solved by using Atomic Reactor instead of my custom hacky script:-)</div><div><br></div><div><br></div><div>Cheers,</div><div>Vašek</div><div><div class="h5"><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"> </div></blockquote><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"><div dir="ltr"><div><br></div><div>I am not sure what you mean by " built image would be deployed to openshift instance".</div></div></blockquote><div> </div></span><div> I was saying about building the docker container images in openshift for the build, test, delivery environments.</div><div> </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"><div dir="ltr"><div><br></div><div>My idea would be to go with the yaml files I saw in cccp-index and rtnpro's example repo as an UI right now - keep the code as little as possible. Hook it up to my example with some scripting, setup OpenShift and registry and try to get whole workflow working.</div></div></blockquote><div> </div><div>Yes, I was going through the same. I tried with building the example you have put. I am going through the cccp-index and yaml file to add with the example you have put. </div><span><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"><div dir="ltr"><div> </div></div></blockquote><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"><div dir="ltr"><div> </div></div></blockquote><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"><div dir="ltr"><div></div><div>I as a developer want to add a yaml file to my repo and submit my repo url somewhere, so that it gets rebuilt, tested and pushed to a given registry regularly (like 4 times a day for start). I also want to be notified about new build and test results.</div></div></blockquote><div> </div></span><div>Yes, this yaml will help to handle all the linking and container management stuff.</div><span><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"><div dir="ltr"><div> <br></div></div></blockquote><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"><div dir="ltr"><div></div><div>Done:-) We can polish it later.</div><div><br></div><div>Makes sense?</div><div><br></div></div></blockquote></span><div>Sure, going ahead with this.</div><div><br></div><div>Regards</div><span><font color="#888888"><div>Bamacharan</div></font></span><div><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"><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, Feb 10, 2016 at 12:47 PM, Bamacharan Kundu <span dir="ltr"><<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a>></span> wrote:<br></div></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"><div><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Feb 10, 2016 at 4:30 PM, Karanbir Singh <span dir="ltr"><<a href="mailto:kbsingh@centos.org" target="_blank">kbsingh@centos.org</a>></span> wrote:<br><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">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<span><br>
On 10/02/16 07:29, Bamacharan Kundu wrote:<br>
> Hi,<br>
><br>
> Vaclav presented the build pipeline very nicely and this would<br>
> take out lot of tension for building the code, checking the code<br>
> standards and test cases from the developer.<br>
><br>
> I would like to add few points on this.<br>
><br>
> On Tue, Feb 9, 2016 at 8:08 PM, Vaclav Pavlin <<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a><br>
</span><span>> <mailto:<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>>> wrote:<br>
><br>
><br>
> Hi all,<br>
><br>
> As KB wrote, I brought up the idea of using OpenShift as a glue<br>
> (i.e. workflow controller). The result can be found here:<br>
><br>
> <a href="https://github.com/vpavlin/cccp-demo-openshift" rel="noreferrer" target="_blank">https://github.com/vpavlin/cccp-demo-openshift</a><br>
><br>
> TL;DR:<br>
><br>
> The repository contains OpenShift Template defining the workflow -<br>
> build,test, delivery and (very poorly) implements the steps through<br>
> Docker images (i.e. Dockerfiles and run scripts).<br>
><br>
> The developer should do only git push to his VCS and this should<br>
> trigger the build process in the pipeline.<br>
<br>
</span>in an onprem story that would map well, but note that were aiming to<br>
run a hosted service with a distinct UI ( even if the UI is no UI )<br></blockquote><div> </div></span><div>Yes, now I got it. I had a thought to minimize the number of Dockerfiles,</div><div>so that the user does not get confused of.</div><span><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">
<span><br>
><br>
> In this TDD process all the environments (including the build,<br>
> test, delivery) would be created as a container and once the step<br>
> is over it will destroy the environment. As output this will<br>
> generate a application runtime along with the successfully built<br>
> application code to registry.<br>
><br>
> As you mentioned this would be tagged with test along with jenkins<br>
> build id, so that developer or QA can trace for which commit this<br>
> is built.<br>
><br>
> Then for the next stages, successfully built image would be<br>
> deployed to openshift instance to get through the test, delivery<br>
> stages checking, along with the quality gates.<br>
><br>
> all the stages should be linked to pipeline and should be easily<br>
> re-producible so that any one can check or regenerate the issues<br>
> instantly.<br>
<br>
</span>add another dimension there - collection of related containers, ie.<br>
the entire microservice should be reproduceable.<br>
<span><br></span></blockquote></span><div>This means system needs to maintain all the linking and volume sharing </div><div>of the components. </div><span><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"><span>
><br>
> It's easily runnable in Vagrant with use of Project Atomic<br>
> Developer Bundle.<br>
><br>
> If you are interested in more info, I'd suggest to read the readme<br>
> in the repo, I hope it summarizes it clearly.<br>
><br>
> It's a very minimal demo, but I think it suggests the path, which<br>
> could take us to the Unicorns land, quite well:).<br>
><br>
> Let me know in case of any questions, suggestions or requests for<br>
> guidance in case anybody decides to take this further.<br>
><br>
> I would like to take this further, please let me know if my<br>
> thought process is in the same line as yours or any changes,<br>
> suggestions.<br>
<br>
</span>we need to work through whats needed to now integrate with the<br>
cccp-index content, and then map that back to deliverables. I had<br>
asked Zeeshan to look at registry side for delivery space, unsure how<br>
far he's gotten with that.</blockquote><div> </div></span><div>I believe, I should look for integration with cccp-index content?</div><div><br></div><div>Regards</div><div>Bamacharan</div></div><div><br></div>-- <br><div><span>Bamacharan Kundu<br>IRC Nick- bamachrn<br></span><a href="http://bamacharankundu.wordpress.com/" target="_blank">http://bamacharankundu.wordpress.com/</a><br></div>
</div></div>
<br></div></div><span>_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
<br></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Developer Experience Team<br>Brno, Czech Republic<br>Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a><br></div></div><div><br></div><div><br></div></div></div></div></div>
</font></span></div>
<br>_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
<br></blockquote></div></div></div><div><div><br><br clear="all"><div><br></div>-- <br><div>Bamacharan Kundu<br>IRC Nick- bamachrn<br><a href="http://bamacharankundu.wordpress.com/" target="_blank">http://bamacharankundu.wordpress.com/</a><br></div>
</div></div></div></div>
<br>_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
<br></blockquote></div></div></div><div><div class="h5"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Developer Experience Team<br>Brno, Czech Republic<br>Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a><br></div></div><div><br></div><div><br></div></div></div></div></div>
</div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Developer Experience Team<br>Brno, Czech Republic<br>Phone: +420 739 666 824<br></div></div><div><br></div><div><br></div></div></div></div></div>
</div>