Talk in English - US at Dutch PHP Conference 2017
Short URL: https://joind.in/talk/4f274
(QR-Code (opens in new window))
Continuous Delivery (CD) allows for automated testing, immediate user feedback and reliable releases. However, for many companies, implementation of a complete CD pipeline remains an elusive goal, especially in environments dominated by PHP. Moreover, most existing CD solutions focus on a single pipeline, rather than allowing the development of several parallel features.
This presentation details a ready-made solution tailored to the requirements of PHP development that we call nFlow. It uses familiar tools, including JIRA, Git, Jenkins, Docker and Kubernetes. nFlow advances beyond basic CD by offering integrated test environments, parallel feature development and deployment-on-demand. Integrated test environments bundle your constellation of applications into a single test environment, allowing you to test your new feature’s interaction with your complete application landscape. If you need to develop several features in parallel, nFlow creates unique branches and test environments for each new feature. Finally, once you complete your feature, nFlow automatically merges it with the master branch, and integrates these new changes with all parallel features still in development, and deploys it to production via Kubernetes. We offer steps easy enough for an aspiring devops to follow, should you wish to develop your own CD pipeline. We will show how this works in a live demo!
Comments
Comments are closed.
Feature branching on steroids, continuous delivery but no continuous integration. Feature branching has serious drawbacks and none of them were mentioned.
The examples at the end took a bit too long which left no room for questions.
The demo took up most of the talk, which left very little room for further explanation, the reasoning behind your tool, and the various drawbacks and issues that you have encountered and the lessons you've learned (I'm sure there are some). Unfortunately no time for questions either.
You were a little hard to understand at times, partly because you moved / turned out of the microphone's reach, partly because of nerves?
Tip: don't use (small) black font on a blue background, that makes the text very hard to read (especially from the back of the room).
I hoped you could give some more insights in your Kubernetes setup for a PHP application (multi-container vs single container, fixtures, scalability, etc.). No room voor questions because the demo took too long.
So the this solution works on simple single projects without complex systems but didn't learn anything.
It was a interesting talk. But instead of doing a live demo I would had like to see a more insight in how Coosto had realized this and why they had choosen to do so.
And why talking about a tool that only Coosto uses and at this moment is not open source.