Software Engineering Using Devops - a Silver Bullet?

Total Page:16

File Type:pdf, Size:1020Kb

Software Engineering Using Devops - a Silver Bullet? UPTEC IT 19 002 Examensarbete 30 hp Januari 2019 Software Engineering using DevOps - a Silver Bullet? Mikaela Eriksson Institutionen för informationsteknologi Department of Information Technology Abstract Software Engineering using DevOps - a Silver Bullet? Mikaela Eriksson Teknisk- naturvetenskaplig fakultet UTH-enheten Today we have technology that help us scan millions of medical databases in a glimpse of an eye and self-driving cars that are outperforming humans at driving. Besöksadress: Technology is developing so fast that new updates in the technology world are Ångströmlaboratoriet Lägerhyddsvägen 1 commonplace to us and we are more often frustrated in case something is not up Hus 4, Plan 0 to speed. Technology is moving so quickly and in order for humans to keep up with the development needed in the tech business, different methodologies for how to Postadress: optimise the development process have been applied, some that work better than Box 536 751 21 Uppsala others. But just as fast as the technology changes, the methodologies used change with them. Recently a new term has entered the methodologies field. This Telefon: term is said to bring faster deployment, decreased failures and improved the 018 – 471 30 03 loyalties within the teams. The term in question, is called DevOps. Telefax: 018 – 471 30 00 This study is about uncovering the world of DevOps. This thesis is exploring the term in real teams in order to find out whether or not DevOps is the silver bullet it Hemsida: makes out to be. The study is based on ten interviews with people at different http://www.teknat.uu.se/student organisations, using DevOps, and will find out how these interviewees use and feel about DevOps. Found in these interviews is that both the involvement in, interpretation and implementation of the term varies between the interviewees. Nothing was all the same between them. All interviewees were very positive about the term and its contributions to the process and would definitely implement it in any new team. However, also found is that development in organisations is leaning towards becoming more single minded. When creating and reforming teams, organisations rather exclude constellations of different human thoughts and departments in order to rely on different development platforms instead. To conclude from this is that DevOps might take away work from collaborating humans in favour of the speed we achieve in the assisting technologies. This in a possible alarming way since single minded teams can miss important aspects in development which can have a dangerous outcome. Even though this might be a truth, DevOps is seen as something very positive and could just be the silver bullet it is talked about it to be, but this only if each team can interpret it, implement it and use it in their own way. Handledare: Maryam Alizadeh Ämnesgranskare: Åsa Cajander Examinator: Lars-Åke Nordén UPTEC IT 19 002 Tryckt av: Reprocentralen ITC Software Engineering using DevOps - a Silver Bullet? Sammanfattning Idag har vi teknik som hj¨alper oss att skanna miljontals medicinska databaser p˚aett ¨ogonblick och sj¨alvk¨orande bilar som ¨ar b¨attre ¨an oss p˚aatt k¨ora bil. Tekniken utvecklas s˚asnabbt att nya uppdateringar i teknikv¨arlden ¨ar vardagsmat, och vi blir l¨att frustrerade om n˚agotinte g˚ari den h¨oga hastigheten vi f¨orv¨antar oss. Tekniken r¨or sig s˚asnabbt nuf¨ortiden och f¨or att vi m¨anniskor ska kunna f¨olja med i den utveckling som beh¨ovs inom tekniken, har olika metoder f¨or hur man optimerar utvecklingsprocesser till¨ampats. Men lika snabbt som tekniken ¨andras, f¨or¨andras de me- toder som anv¨ands med dem. Nyligen har en ny term inom metoder uppkommit. Denna term s¨ags ge snabbare implementering, f¨arre misslyckanden och f¨orb¨attrad lojalitet inom team. Termen i fr˚aga kallas DevOps. Denna studie handlar om att dyka ner i DevOps v¨arld f¨or att utforska om termen ¨ar den silverkula som det p˚avisarsig vara. Studien ¨ar baserad p˚atio intervjuer med personer fr˚anolika organisa- tioner som sagt att de anv¨ander DevOps och har som m˚alatt ta reda p˚ahur dessa intervjuade anv¨ander och upplever DevOps. Funnet i dessa intervjuer ¨ar att b˚adeinblandning i, tolkning och genomf¨orande av termen varierar mellan de intervjuade. Ingenting som sas var det samma mellan intervjuerna. Alla intervjuade var mycket positiva ¨over att ha implementerat DevOps, vad det bi- dragit med till processer och skulle definitivt implementera DevOps i nya team. Men det kan ocks˚a konstateras att utvecklingen i organisationer ¨ar p˚av¨ag mot att bli mer enkelsinnad. Vid skapande och reformering av team utesluter organisationer hellre konstellationer av olika m¨anskliga tankar och avdelningar f¨or att ist¨allet f¨orlita sig p˚aolika utvecklingsplattformar. Slutsatsen ¨ar att DevOps kan orsaka att team tar bort samarbete mellan m¨anniskor till f¨orm˚anf¨or den hastighet de uppn˚ar i tekniken. Detta ¨ar potentiellt alarmerande d˚aenformiga team kan missa viktiga aspekter i sin utveckling vilket kan leda till allvarliga konsekvenser. Aven¨ om detta kan vara en sanning s˚ases DevOps som n˚agotmycket positivt och kan ¨and˚avara den silverkulan som det talas om att det ska vara, men enbart om varje team kan tolka det, implementera det och anv¨anda det p˚asitt eget s¨att. 2 Software Engineering using DevOps - a Silver Bullet? Acknowledgements This study would not have been possible to complete without the help and support from the following people which deserve a special thank you. Asa˚ Cajander. Thank you for agreeing to be reviewer and for coming up with the idea to discover DevOps and to view it from a human-computer interaction point of view. Thank you for helping me with the process, insightful thoughts and for reading and commenting on my report almost every week, it has been gold. Also thank you for saying that "good enough" is a more than an acceptable result, without that this report would have been much harder and not as fun to write as it was. Maryam Alizadeh. Thank you for being there in exactly the right way, for always asking in case you can help and for setting up things to enable the interviews and presentation. Thank you for taking time reading my report and supporting me with ideas along the way. Omegapoint. Thank you for the opportunity to write this thesis at your company and office even though it always was very cold. You all have been so including and kind that it is hard to leave. Especially thank you to Tatiana, Bettan, Apparna, Gustav and the others around the table for making the time fly with laughter, hopefully the connections will remain. Mum and dad. Thank you dad for helping me with all your knowledge about the subject, for set- ting up interviews and for giving important suggestions at the last hours. Especially thank you for your enthusiasm about the subject chosen, it was much appreciated. Thank you mum for the support in the darkest times, for always believing in me and for always being the inspiration. Mum and dad, this report is dedicated to you. 3 Software Engineering using DevOps - a Silver Bullet? Contents 1 Introduction 6 2 Background 8 2.1 Interpretation of DevOps . 8 2.2 Platforms and Tools . 10 2.2.1 Amazon Web Services . 10 2.2.2 Microsoft Azure . 11 2.2.3 Other Tools . 11 3 Scope, Goal and Limitations 13 3.1 Research Questions . 13 3.2 Limitations . 13 4 Related Work 14 4.1 Interpretation and Implementation of DevOps . 14 4.2 Involvement in the DevOps Process . 14 4.3 Automating Work . 15 4.4 Collaboration Between Teams with DevOps Implemented . 15 4.5 Effects of Implementing DevOps . 16 4.6 The Contribution of this Study . 16 5 Method 17 5.1 Preparatory Research . 17 5.2 The Interview Process . 17 5.2.1 Quantitative Research . 18 5.2.2 Interviewees . 18 5.2.3 Interviews . 19 5.3 Analysing Interviews . 20 6 Results 22 6.1 Interpretation and Implementation of DevOps . 22 6.2 Involvement in the DevOps Process . 23 6.3 Automating Work . 24 6.4 Collaboration Between Teams with DevOps Implemented . 25 4 Software Engineering using DevOps - a Silver Bullet? 6.5 Effects of Implementing DevOps . 26 7 Discussion 28 7.1 Interpretation and Implementation of DevOps . 28 7.1.1 The Developers Own Responsibility . 28 7.1.2 DevOps Used Before as Continuous Integration . 30 7.1.3 Automation . 30 7.1.4 Implementation of DevOps . 31 7.2 Involvement in the DevOps Process . 32 7.2.1 Establishment of the Development Team and the Operations Team . 32 7.2.2 The Organisations with no Operations Team . 33 7.3 Automating Work . 34 7.3.1 Manual Work . 34 7.3.2 Platforms . 35 7.4 Collaboration Between Teams with DevOps Implemented . 35 7.4.1 Change in Team Collaboration with DevOps . 36 7.4.2 Team Prioritised in the DevOps Process . 36 7.5 Effects of Implementing DevOps . 37 7.5.1 Initial Thought of Implementing DevOps . 37 7.5.2 Changes in the Process by Using DevOps . 38 7.6 General Discussion . 39 8 Conclusion 40 9 Future Work 43 10 References 44 5 Software Engineering using DevOps - a Silver Bullet? 1 Introduction Technology is amazing. We have inventions that allow us to visualise things in the real space with augmented reality, computer systems that out-compete human physicians when it comes to finding the right diagnosis in the health business and self-driving cars that slowly are taking over driving from us humans.
Recommended publications
  • Devops and Testers White Paper
    White Paper DevOps and Testers DevOps is part of an overall approach that organizations use to deliver software frequently and with high quality. The most obvious outcome of successful DevOps implementations is the reduction in the time it takes for software changes to transition from an idea to production. What Does DevOps Mean If you are an experienced DevOps Automated tools and processes practitioner, we hope that you are used in system configuration, for Testers might still find the article useful. If the build process, testing, the Background you are not a tester, we hope that deployment to test, staging and The DevOps movement (for want you will at least see the tester’s production environments, post- of a better label) is progressing perspective. deployment monitoring, evaluation, rapidly. Like many other and operations. movements in the industry, the What Is DevOps? speed of adoption accelerates Is DevOps Just About faster than the definition of the Simplistically, DevOps is a label movement itself. DevOps is still to describe an ecosystem in Tools? not well defined and the nuances which development teams and At one level, the goal of DevOps of culture, the emergent capability systems operations teams work is to eliminate bottlenecks in of new technologies, and range of more closely together. In the the delivery pipeline through (mostly successful) case studies so-called delivery pipeline, from automation. But the automation means that the issues at hand are committing source code to putting of staged processes still still widely debated.1 code into production, developers requires governance. Most accommodate and automate some automated processes are not Depending on who you talk to, of operations activities.
    [Show full text]
  • IBM Developer for Z/OS Enterprise Edition
    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
    [Show full text]
  • Magic Quadrant for Application Release Automation
    Magic Quadrant for Application Release Automation Published: 27 September 2017 ID: G00315074 Analyst(s): Colin Fletcher, Laurie F. Wurster The ARA market is rapidly evolving in response to growing enterprise requirements to both scale DevOps initiatives and improve release management agility across multiple cultures, processes and generations of technology. This research helps I&O leaders make better-informed decisions. Strategic Planning Assumption By 2020, 50% of global enterprises will have implemented at least one application release automation solution, up from less than 15% today. Market Definition/Description Application release automation (ARA) tools provide a combination of automation, environment modeling and release coordination capabilities to simultaneously improve the quality and the velocity of application releases. ARA tools enable best practices in moving application-related artifacts, applications, configurations and even data together across the application life cycle process. These tools are a key part of enabling the DevOps goal of achieving continuous delivery with large numbers of rapid, small releases. Approximately seven years old, the ARA solution market reached an estimated $228.2 million in 2016, up 31.4% from $173.6 million in 2015. The market is continues to be expected to grow at an estimated 20% compound annual growth rate (CAGR) through 2020. Magic Quadrant Figure 1. Magic Quadrant for Application Release Automation Source: Gartner (September 2017) Vendor Strengths and Cautions Arcad Software Founded in 1992, Arcad Software is a privately held company headquartered in Chavanod, France. The company was started by its founder to deliver automation-oriented solutions supporting the Page 2 of 28 Gartner, Inc. | G00315074 IBM i (introduced as AS/400, then later renamed eServer iSeries) platform.
    [Show full text]
  • Ebook Devops Toolchain.Pdf
    DevOps Toolchain 1 Introduction accordingly based on the problem at hand. DevOps may need little introduction these days, Similarly, most systems administrators possess but many are still at a loss to explain precisely competent programming abilities for traversing what the movement entails. Some emphasize the the stack—on top of the requisite skills for portmanteau of the two terms, stating that the managing IT operations. The industry has heart of DevOps is the collaboration between been quick in attaching new labels to these developers and operations staff. Others choose emerging hybrid roles: DevOps Engineer and to focus on the tools and the problems they solve, DevOps Specialist being the most common. singing the praises of DevOps for fixing their Notwithstanding, the key takeaway is that no respective infrastructure woes. Tools—though single IT skill is more important or valuable than crucial enablers of the movement—only form part another; subsequently, many different tools are of the equation. DevOps encompasses cultural required to do the job effectively. So as DevOps innovation, a breaking down of walls and silos is comprised of a group of concepts clustered between software development, operations, around the premise of continuous software and QA/ testing—in addition to the tools and delivery, these concepts in turn encompass a methodologies enabling this transformation. range of associated tools for fulfilling particular Ultimately, the definition of DevOps varies per functions. organization. Since its meaning depends heavily on the audience and context in question, general All in all, these complementary tools fill out the discussions around the true definition of DevOps DevOps toolchain, unifying the best elements are for the most part inconsequential.
    [Show full text]
  • Designing Software Architecture to Support Continuous Delivery and Devops: a Systematic Literature Review
    Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review Robin Bolscher and Maya Daneva University of Twente, Drienerlolaan 5, Enschede, The Netherlands [email protected], [email protected] Keywords: Software Architecture, Continuous Delivery, Continuous Integration, DevOps, Deployability, Systematic Literature Review, Micro-services. Abstract: This paper presents a systematic literature review of software architecture approaches that support the implementation of Continuous Delivery (CD) and DevOps. Its goal is to provide an understanding of the state- of-the-art on the topic, which is informative for both researchers and practitioners. We found 17 characteristics of a software architecture that are beneficial for CD and DevOps adoption and identified ten potential software architecture obstacles in adopting CD and DevOps in the case of an existing software system. Moreover, our review indicated that micro-services are a dominant architectural style in this context. Our literature review has some implications: for researchers, it provides a map of the recent research efforts on software architecture in the CD and DevOps domain. For practitioners, it describes a set of software architecture principles that possibly can guide the process of creating or adapting software systems to fit in the CD and DevOps context. 1 INTRODUCTION designing new software architectures tailored for CD and DevOps practices. The practice of releasing software early and often has For clarity, before elaborating on the subject of been increasingly more adopted by software this SLR, we present the definitions of the concepts organizations (Fox et al., 2014) in order to stay that we will address: Software architecture of a competitive in the software market.
    [Show full text]
  • Devops Point of View an Enterprise Architecture Perspective
    DevOps Point of View An Enterprise Architecture perspective Amsterdam, 2020 Management summary “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”1 Setting the scene Goal of this Point of View In the current world of IT and the development of This point of view aims to create awareness around the IT-related products or services, companies from transformation towards the DevOps way of working, to enterprise level to smaller sizes are starting to help gain understanding what DevOps is, why you need it use the DevOps processes and methods as a part and what is needed to implement DevOps. of their day-to-day organization process. The goal is to reduce the time involved in all the An Enterprise Architecture perspective software development phases, to achieve greater Even though it is DevOps from an Enterprise Architecture application stability and faster development service line perspective, this material has been gathered cycles. from our experiences with customers, combined with However not only on the technical side of the knowledge from subject matter experts and theory from organization is DevOps changing the playing within and outside Deloitte. field, also an organizational change that involves merging development and operations teams is Targeted audience required with an hint of cultural changes. And last but not least the skillset of all people It is specifically for the people within Deloitte that want to involved is changing. use this as an accelerator for conversations and proposals & to get in contact with the people who have performed these type of projects.
    [Show full text]
  • Continuous Testing for Devops Evolving Beyond Simple Automation
    Technical Whitepaper 1 Continuous Testing for DevOps Evolving Beyond Simple Automation INTRODUCTION DevOps represents a cultural shift that stresses collaboration be- on acceleration. Moreover, adopting a bona fide Continuous Testing tween the business, developers, and IT professionals. Software test process (more than just automated tests running regularly) helps automation can enhance these connections and help organizations promote all of the core pillars of DevOps: Culture, Automation, Lean, achieve desired SDLC acceleration, but it’s important to recognize Metrics, and Sharing. that automation is just one piece of the DevOps puzzle. In this paper, we’ll explore why and how Continuous Testing’s real- Since testing is often one of the greatest constraints in the SDLC, time objective assessment of an application’s business risks is a optimizing quality processes to allow testing to begin earlier, as well critical component of DevOps. as shrink the amount of testing required, can have a marked impact DEVOPS PRINCIPLES There are several key pieces to understanding DevOps revolutions and they are often brought about by a compelling event at an organization, such as a shift to agile. As organizations start to move into an agile development methodology, they start to uncover other processes that can be accelerated, such as delivery by DevOps and testing by Continuous Testing. The acceleration that is set in motion via agile makes it necessary to accelerate the release schedule. In order to ensure a successful release, an organization must adopt continuous testing to make sure the conveyer belt does not break down. The modernization maturity model has these three distinct phases: AGILE Agile software development is a different way of thinking about approaching the challenge of development time.
    [Show full text]
  • Continuous Delivery for Every Team
    Continuous Delivery for Every Team Six ways CA Continuous Delivery Director can help you become a modern software factory Keeping up with customer demand—and getting ahead of the competition—means you must continuously deliver high-quality apps and experiences. In the modern software factory, you’ll find: Application releases are occurring at increased volumes, with greater frequency and speed.1 33% Release daily or “Cloud First” is Microservice more frequently 66% becoming a global architectures and 33% priority. container-based apps In 15 months, 80 percent are the new norm. Release weekly of all IT budgets will be 83 percent of organizations committed to cloud apps are actively using containers 2 and solutions. today.3 1 CA Technologies DevOps Research, prepared by Spiceworks, February 2017 2 Forbes, “2017 State of Cloud Adoption and Security,” April 2017 3 Ibid 02 But how do you become a modern software factory when you’re still facing challenges like: • Manual Processes: Manual, ad hoc release and testing processes do not scale in a multi-app, multi-release pipeline. And increased deployment frequency and speed through automation exacerbate the issue. • Testing Bottlenecks: Testing is critical, but a siloed, time- consuming and manual part of the release cycle. In fact, 66 percent still use Microsoft Excel®, Microsoft Word® and email to track testing.4 • Evolving Tech: DevOps toolchains and technologies are constantly evolving, putting pressure on teams to balance new capabilities with existing investments. • Limited Visibility: The proliferation of moving parts requires that you establish a big picture view of the pipeline to continuously improve the speed and quality of releases.
    [Show full text]
  • Gartner Magic Quadrant for Enterprise Agile Planning Tools, April 2019
    13/09/2019 Gartner Reprint Licensed for Distribution Magic Quadrant for Enterprise Agile Planning Tools Published 18 April 2019 - ID G00361074 - 40 min read By Analysts Keith Mann, Mike West, Thomas Murphy, Nathan Wilson As organizations mature their enterprise-scale agile capabilities, established vendors refine their offerings and new providers emerge. This Magic Quadrant evaluates 17 vendors of enterprise agile planning tools to help you make the right choice for your organization. Market Definition/Description This document was revised on 26 April 2019. The document you are viewing is the corrected version. For more information, see the Corrections (http://www.gartner.com/technology/about/policies/current_corrections.jsp) page on gartner.com. Enterprise agile planning (EAP) tools help organizations make use of agile practices at scale to achieve enterprise-class agile development. This is achieved by supporting practices that are business-outcome-driven, customer-centric, collaborative and cooperative, in conjunction with continual stakeholder feedback. These tools represent an evolution from project-centric agile tools and traditional application development life cycle management (ADLM) tools. The majority of products in the EAP tool market play into the overall ADLM product set, acting as hubs for the definition and management of work item tracking. There is a relationship between EAP tools, project portfolio management (PPM) tools and product roadmapping tools. Traditional PPM tools provide the high-level planning and resource management enterprises demand, but may lack enterprise-class agile development support. EAP tools, for their part, may not support project management outside agile frameworks. (Gartner has a separate Magic Quadrant for PPM, the latest being “Magic Quadrant for Project Portfolio Management, Worldwide”).
    [Show full text]
  • The Practical Blueprint to Continuous Delivery Executive Summary
    The Practical Blueprint to Continuous Delivery Executive Summary CA Technologies, A Broadcom Company, proposes a four-stage blueprint to continuous delivery to assist enterprises at any stage of their DevOps journey. This plan can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic® Continuous Delivery Automation, 40-plus years of business automation experience, and the proven tools and practices the company is already leveraging. As the only vendor that automates within the toolchain (steps one and two) and across the toolchain (steps three and four), CA Technologies is in a unique position to help enterprises at every stage of their progression. Our tool-agnostic, cross-platform and multi- stack technology means developers can continue using the tools they are most comfortable with, while DevOps teams can collaboratively build automated, production-ready deployment processes that make operations comfortable. CA Technologies offers a DevOps Maturity Assessment that shows on which of the four steps an organization sits, and compares its current state with that of its competitors, its industry and its competition globally. Using the assessment findings will give companies a blueprint to guide them up to the next level on the road to enterprise agility as quickly and safely as possible. 2 Step 1: Manual and Scripting Participation in our DevOps Maturity Assessment will deliver a continuous delivery roadmap that contains a blueprint for DevOps throughout the enterprise. Customers will be able to compare their current state with their competitors, their industry and globally. Manual steps will be identified and documented, then replaced with automated tasks and workflows.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • Q Advisors' Cloud Native/Devops Private Vendors Matrix
    Q Advisors' Cloud Native/DevOps Private Vendors Matrix By Dmitry Netis & Jordan Rupar / 4.7.2020 Q Advisors assembled over 100 startups in the cloud native Kubernetes ecosystems, peddling various software offerings across the following six distinct cloud native / Kubernetes market sub-segments: Continuous Integration / Development Tools Testing & Monitoring Continuous Delivery (“Dev”) (“Mon”) (“CI/CD”) Product Deployment, Service Mesh Security Management & Orchestration (“Run”) (“Sec”) (“Ops”) Sector Company Description Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines. Buildkite is a CI and build CI/CD automation tool that combines build infrastructure with the convenience of a managed, centralized web UI. CircleCI provides online automated testing and continuous CI/CD integration tools for developers worldwide. CloudBees developed Jenkins, a tool for continuous delivery both on-premises and in the cloud. In 2018, CloudBees acquired CI/CD Codeship, a provider of CI/CD as a cloud-based service, a move that broadened its portfolio for organizations of all sizes. Codefresh provides powerful, fast, and simple CI/CD pipelines. Each CI/CD step in a Codefresh CI/CD pipeline is its own container, enabling speed, modularity, and flexibility. GitLab is a continuous integration and deployment tool for the entire DevOps lifecycle. The company also offers Git repository and CI/CD GitLab Serverless that enables enterprises to run serverless workloads on any cloud using Google’s Knative. Harness uses machine learning to simplify the process of delivering code from artifact into production. Its platform includes various CI/CD features, such as pipeline builder, workflow wizard, continuous verification, automated rollback, secrets management, audit trails, real-time delivery analytics, and GitOps.
    [Show full text]