Last October I had the honor of giving a talk at Velocity Conference in Amsterdam, along with our CTO, Anders Wallgren.
Our talk was targeted at developers and engineering managers who need to achieve centralized management and visibility into the end-to-end software development pipeline. Judging by the over flow in the room and the responses from attendees — this is a problem a lot of organizations are facing these days.
Software delivery pipelines are becoming more and more complex, and are integrating a myriad of open source tools, frameworks, and infrastructures. From project management and defect tracking (JIRA, Bugzilla, etc.), SCM and configuration management (GIT, Chef, Puppet), CI (Jenkins, Travis-CI), Testing (Selenium), to databases (Hadoop, MySQL) and infrastructure and cloud platforms (AWS, Open Stack, Docker) – modern application delivery today involves and depends on a wide range of open source tools.
To improve developer productivity and resource utilization – and to enable enterprise-scale, cross-project visibility and shorter time to market – many organizations are working to automate and orchestrate the entire tool chain across the end-to-end delivery pipeline.
‘Automate all the things‘ is a key tenant to any DevOps or Continuous Delivery initiative. In this session, Anders and I shared not only why you would want to ‘automate all the thing’, but how to get started on this journey to get it right.
We shared the story of how a $40 billion company (Huawei) managed to plug-in all their disparate CI and CD tools throughout the software lifecycle into acentralized orchestration solution – creating a world-class internal dev/test cloud servicing 50,000 engineers and thousands of applications across their organization.
This case study is used to illustrate the prerequisites, best practices, and pitfalls to avoid when implementing an end-to-end orchestration strategy.
Watch the Video Of Our Talk:
This article was written by Tanay Nagjee.