-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/02/16 07:29, Bamacharan Kundu wrote: > Hi, > > 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. > > I would like to add few points on this. > > On Tue, Feb 9, 2016 at 8:08 PM, Vaclav Pavlin <vpavlin at redhat.com > <mailto:vpavlin at redhat.com>> wrote: > > > Hi all, > > As KB wrote, I brought up the idea of using OpenShift as a glue > (i.e. workflow controller). The result can be found here: > > https://github.com/vpavlin/cccp-demo-openshift > > 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). > > The developer should do only git push to his VCS and this should > trigger the build process in the pipeline. in an onprem story that would map well, but note that were aiming to run a hosted service with a distinct UI ( even if the UI is no UI ) > > 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. > > 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. > > 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. > > 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. add another dimension there - collection of related containers, ie. the entire microservice should be reproduceable. > > 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. > > 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. we need to work through whats needed to now integrate with the cccp-index content, and then map that back to deliverables. I had asked Zeeshan to look at registry side for delivery space, unsure how far he's gotten with that. Once we have the end to end scaffolding in place, we should then work through a few use cases, for the service side, and look at scope of development needed from that point on. - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWuxhqAAoJEI3Oi2Mx7xbt/k4H/icQgFtEw5M8CQSQPi70h4XZ 311u5UMKzR0Mp3SMKIdtf4ROs5wkoRm51+Fd3O+QiF1a5i4WQhiKX6loryvI41Y6 h0/tAFue8YxQwf5+1gYJk0cAoxxW7Lya9Senbh/SXZSu9QPS7S+My1MTUXQP8lM8 a/5MexKuY1GjJcvxVz3KPw8Pe6lGfzErmZiwg8VbhJvA2NfOvcicsreUWcRS/1df Z4b4oY35LmdlWLItr1UBnqTrZYa6xeIX6bOmi3bO+ICrIlkWwRn7xglFw4b28Q1F v+jRFXJ646BLjObJtFCAbPDCfMPL2N7pnWOLNbq38OtQyPnsJcQYe7oE1NXK/SY= =DoIx -----END PGP SIGNATURE-----