<div dir="ltr">I was informed by few people that my how to at <a href="https://github.com/vpavlin/cccp-demo-openshift">https://github.com/vpavlin/cccp-demo-openshift</a> does not work with ADB 1.7.0 so I fixed it.<div><br></div><div>Adam, there is an oc command the ADB box...try to just copy the commands snippets to terminal and you should be good..don't skip anything:-P</div><div><br></div><div>Vašek</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 17, 2016 at 7:46 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Vesak, KB,<div>      could we meet over bluejeans some time?</div><div>I am confused with what we are trying to achieve and why.</div><div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div>Bamacharan</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 16, 2016 at 6:54 PM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 16/02/16 13:15, Bamacharan Kundu wrote:<br>
> Hi Vašek,<br>
>     Yes, I have created pipeline with a nodejs based<br>
> application(<a href="https://github.com/bamachrn/cccp-demo-test" rel="noreferrer" target="_blank">https://github.com/bamachrn/cccp-demo-test</a>)<br>
> with openshift build system. Openshift template is taking the git repo<br>
> URI as input, and building, testing within the containers.<br>
> As a output this is pushing the ready to run containers to the registry.<br>
><br>
> Went through the atomic reactor for reading index.yaml and cccp.yaml<br>
> written by rtnpro, kbsingh.<br>
><br>
> I am currently working to understand the openshift template and build<br>
> config to automate the build<br>
> on git push or scheduled time.<br>
><br>
> Today I am trying to trigger with Github webhook. This is not triggering<br>
> the build due to my IP being in private network.<br>
</span>> also waiting for the <a href="http://ci.centos.org" rel="noreferrer" target="_blank">ci.centos.org</a> <<a href="http://ci.centos.org" rel="noreferrer" target="_blank">http://ci.centos.org</a>> access to use<br>
<span>> jenkins in build process.<br>
><br>
> Please suggest if there is another way to achieve this.<br>
<br>
<br>
</span>Looks like we need to setup a syncup point<br>
<span><br>
><br>
> Thanks<br>
> Bamacharan<br>
><br>
> On Tue, Feb 16, 2016 at 6:29 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>
>     Hey, any progress here?<br>
><br>
>     Vašek<br>
><br>
>     On Wed, Feb 10, 2016 at 4:19 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>
><br>
>         On Wed, Feb 10, 2016 at 3:33 PM, Bamacharan Kundu<br>
</span><span>>         <<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a> <mailto:<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a>>> wrote:<br>
><br>
>             Hi Vaclav,<br>
><br>
>             On Wed, Feb 10, 2016 at 6:53 PM, Vaclav Pavlin<br>
</span><div><div>>             <<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a> <mailto:<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>>> wrote:<br>
><br>
>                 Hi Bamacharan,<br>
><br>
>                 I'd be careful with per commit builds in case of build<br>
>                 from Dockerfile as it takes time and resources<br>
>                 (presumably a lot of both) because we have to build in<br>
>                 clean env and with --no-cache.<br>
><br>
><br>
>             Why don't we take a layered based aproach, we can take the<br>
>             base image from local system then build it, this will save<br>
>             lot of time? I saw multiple dockerfiles for<br>
>             build,test,delivery which are intern the same image only.<br>
><br>
><br>
>         To un-confuse people who didn't see our IRC convo - the<br>
>         Dockerfiles in cccp-demo-openshift repo represent containers<br>
>         which implement individual steps of the workflow - not the<br>
>         images/containers which are tested and delivered.<br>
><br>
>         To answer  "Why don't we take a layered based aproach": We do,<br>
>         building from Dockerfile follows the layered approach. The<br>
>         problem I am trying to emphasize is that we need clean<br>
>         environment for every build, otherwise we could introduce<br>
>         inconsistency again..But I think this could be easily solved by<br>
>         using Atomic Reactor instead of my custom hacky script:-)<br>
><br>
><br>
>         Cheers,<br>
>         Vašek<br>
><br>
><br>
><br>
><br>
>                 I am not sure what you mean by " built image would be<br>
>                 deployed to openshift instance".<br>
><br>
><br>
>              I was saying about building the docker container images in<br>
>             openshift for the build, test, delivery environments.<br>
><br>
><br>
><br>
>                 My idea would be to go with the yaml files I saw in<br>
>                 cccp-index and rtnpro's example repo as an UI right now<br>
>                 - keep the code as little as possible. Hook it up to my<br>
>                 example with some scripting, setup OpenShift and<br>
>                 registry and try to get whole workflow working.<br>
><br>
><br>
>             Yes, I was going through the same. I tried with building the<br>
>             example you have put. I am going through the cccp-index and<br>
>             yaml file to add with the example you have put.<br>
><br>
><br>
><br>
><br>
><br>
>                 I as a developer want to add a yaml file to my repo and<br>
>                 submit my repo url somewhere, so that it gets rebuilt,<br>
>                 tested and pushed to a given registry regularly (like 4<br>
>                 times a day for start). I also want to be notified about<br>
>                 new build and test results.<br>
><br>
><br>
>             Yes, this yaml will help to handle all the linking and<br>
>             container management stuff.<br>
><br>
><br>
><br>
>                 Done:-) We can polish it later.<br>
><br>
>                 Makes sense?<br>
><br>
>             Sure, going ahead with this.<br>
><br>
>             Regards<br>
>             Bamacharan<br>
><br>
><br>
>                 On Wed, Feb 10, 2016 at 12:47 PM, Bamacharan Kundu<br>
</div></div><span>>                 <<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a> <mailto:<a href="mailto:bamachrn@gmail.com" target="_blank">bamachrn@gmail.com</a>>> wrote:<br>
><br>
><br>
><br>
>                     On Wed, Feb 10, 2016 at 4:30 PM, Karanbir Singh<br>
</span><span>>                     <<a href="mailto:kbsingh@centos.org" target="_blank">kbsingh@centos.org</a> <mailto:<a href="mailto:kbsingh@centos.org" target="_blank">kbsingh@centos.org</a>>> wrote:<br>
><br>
>                         -----BEGIN PGP SIGNED MESSAGE-----<br>
>                         Hash: SHA1<br>
><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> <mailto:<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>><br>
</span>>                         > <mailto:<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a> <mailto:<a href="mailto:vpavlin@redhat.com" target="_blank">vpavlin@redhat.com</a>>>><br>
<div><div>>                         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>
>                         in an onprem story that would map well, but note<br>
>                         that were aiming to<br>
>                         run a hosted service with a distinct UI ( even<br>
>                         if the UI is no UI )<br>
><br>
><br>
>                     Yes, now I got it. I had a thought to minimize the<br>
>                     number of Dockerfiles,<br>
>                     so that the user does not get confused of.<br>
><br>
><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>
>                         add another dimension there - collection of<br>
>                         related containers, ie.<br>
>                         the entire microservice should be reproduceable.<br>
><br>
>                     This means system needs to maintain all the linking<br>
>                     and volume sharing<br>
>                     of the components.<br>
><br>
>                         ><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>
>                         we need to work through whats needed to now<br>
>                         integrate with the<br>
>                         cccp-index content, and then map that back to<br>
>                         deliverables. I had<br>
>                         asked Zeeshan to look at registry side for<br>
>                         delivery space, unsure how<br>
>                         far he's gotten with that.<br>
><br>
><br>
>                     I believe, I should look for integration with<br>
>                     cccp-index content?<br>
><br>
>                     Regards<br>
>                     Bamacharan<br>
><br>
>                     --<br>
>                     Bamacharan Kundu<br>
>                     IRC Nick- bamachrn<br>
>                     <a href="http://bamacharankundu.wordpress.com/" rel="noreferrer" target="_blank">http://bamacharankundu.wordpress.com/</a><br>
><br>
>                     _______________________________________________<br>
>                     CentOS-devel mailing list<br>
</div></div>>                     <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
<span>>                     <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>
><br>
><br>
><br>
>                 --<br>
>                 Developer Experience Team<br>
>                 Brno, Czech Republic<br>
</span>>                 Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a> <tel:%2B420%20739%20666%20824><br>
><br>
><br>
><br>
>                 _______________________________________________<br>
>                 CentOS-devel mailing list<br>
>                 <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
<span>>                 <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>
><br>
><br>
><br>
>             --<br>
>             Bamacharan Kundu<br>
>             IRC Nick- bamachrn<br>
>             <a href="http://bamacharankundu.wordpress.com/" rel="noreferrer" target="_blank">http://bamacharankundu.wordpress.com/</a><br>
><br>
>             _______________________________________________<br>
>             CentOS-devel mailing list<br>
</span>>             <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
<span>>             <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>
><br>
><br>
><br>
>         --<br>
>         Developer Experience Team<br>
>         Brno, Czech Republic<br>
</span>>         Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a> <tel:%2B420%20739%20666%20824><br>
<span>><br>
><br>
><br>
><br>
><br>
>     --<br>
>     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>
><br>
><br>
><br>
>     _______________________________________________<br>
>     CentOS-devel mailing list<br>
</span>>     <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a>><br>
<span>>     <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>
><br>
><br>
><br>
> --<br>
> Bamacharan Kundu<br>
> IRC Nick- bamachrn<br>
> <a href="http://bamacharankundu.wordpress.com/" rel="noreferrer" target="_blank">http://bamacharankundu.wordpress.com/</a><br>
><br>
><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>
<br>
<br>
--<br>
</span><span>Karanbir Singh<br>
<a href="tel:%2B44-207-0999389" value="+442070999389" target="_blank">+44-207-0999389</a> | <a href="http://www.karan.org/" rel="noreferrer" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" rel="noreferrer" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" rel="noreferrer" target="_blank">http://www.karan.org/publickey.asc</a><br>
</span><div><div>_______________________________________________<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>
</div></div></blockquote></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><br>_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">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><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>