DOCSLIB.ORG

Winter 2020 Continuous Delivery & Release Automation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

2020 WINTER CUSTOMER SUCCESS REPORT CONTINUOUS DELIVERY & RELEASE AUTOMATION CATEGORY CONTINUOUS DELIVERY & RELEASE AUTOMATION OVERVIEW Continuous delivery is a process that assists developers to create deployment-ready code swiftly and efficiently. It reduces development cycles with workflows, automation, and more to aid developers to write, stage, and test software updates. They need to manually deploy the code written via continuous delivery. In addition, continuous delivery & release automation software solutions enable development teams to save money and time. The applications facilitate a robust feedback cycle that can bolster the strength of a company’s final product. These tools also provide visibility into the development cycle, assisting management, product managers, and team leads to receive deep analytics and insight on development success. Continuous delivery programs go beyond continuous integration till the juncture of being implementation-ready. But unlike continuous deployment platforms, they do not automatically implement code alteration in production after clearing automated testing. 2 Customer Success Report Ranking Methodology The FeaturedCustomers Customer Success ranking is based on data from our customer reference Customer Success Report platform, market presence, web presence, & social Award Levels presence as well as additional data aggregated from online sources and media properties. Our ranking engine applies an algorithm to all data collected to calculate the final Customer Success Report rankings. The overall Customer Success ranking is a weighted average based on 3 parts: Market Leader Content Score is affected by: Vendor on FeaturedCustomers.com with 1. Total # of vendor generated customer substantial customer base & market share. references (case studies, success stories, Leaders have the highest ratio of customer testimonials, and customer videos) success content, content quality score, and social media presence relative to company size. 2. Customer reference rating score 3. Year-over-year change in amount of customer references on FeaturedCustomers platform 4. Total # of profile views on FeaturedCustomers platform Top Performer 5. Total # of customer reference views on FeaturedCustomers platform Vendor on FeaturedCustomers.com with significant market presence and resources and enough Market Presence Score is affected by: customer reference content to validate their vision. 1. Social media followers including LinkedIn, Top Performer's products are highly rated by its Twitter, & Facebook customers but have not achieved the customer base and scale of a Market Leader. 2. Vendor momentum based on web traffic and search trends 3. Organic SEO key term rankings 4. Company presence including # of press mentions Rising Star Company Score is affected by: Vendor on FeaturedCustomers.com that does not 1. Total # of employees (based on social media have the market presence of Market Leaders or and public resources) Top Performers, but understands where the market is going and has disruptive technology. Rising 2. Year-over-year change in # of employees over Stars have been around long enough to establish past 12 months momentum and a minimum amount of customer 3. Glassdoor ranking reference content along with a growing social 4. Venture capital raised presence. 3 2020 Customer Success Awards Check out this list of the highest rated Continuous Delivery & Release Automation software based on the FeaturedCustomers Customer Success Report. 4 OVERALL BEST OF CONTINUOUS DELIVERY & RELEASE AUTOMATION 5 TRUSTED BY ABOUT PUPPET Puppet is driving the movement to a world of unconstrained software change. Its revolutionary platform is the industry standard 182 for automating the delivery and operation of the software that powers everything around us. More than 37,000 Customer references from companies—including more than 75 percent of the Fortune 100—use Puppet’s open source and commercial solutions to adopt DevOps happy Puppet users practices, achieve situational awareness and drive software change with confidence. Headquartered in Portland, Oregon, Puppet is a privately held company with more than 500 employees around the VIEW ALL REFERENCES world. "From the start, we saw Puppet as a key enabler of the services we offer our customers. Puppet let us deliver an easy to manage, customized system, cheaper and more efficiently compared to other configuration management tools on the market. Using anything else would consume too much time and resources for our customers." Guy Naor Founder and CTO, MorphLabs "Configuration management automation is critical to the success of our SaaS-enablement cloud platform. It allows us to be more efficient with human resources and ensures consistency and reproducibility for deployed applications. The community is supportive, and Puppet Labs keeps Puppet evolving to adapt to the ever-changing needs of enterprise IT." Matthew Porter CEO, Contegix “In the future, we would like to help our customers automatically scale, something that we couldn’t turn our attention to previously, due to it being such a large task. But now with Puppet Enterprise, everything has become a lot simpler. This really puts my mind at ease, and I don’t have to worry about it anymore.” Ioan Bercea Technical Director, ResponseConcepts “Automating the actual building of systems means I can concentrate on the other pieces, while Puppet manages building the systems for me.” Bill Wellington Network & System Administrator, DevOps, Fulcrum Technologies 6 7 2020 MARKET LEADERS 8 TRUSTED BY ABOUT ATLASSIAN BAMBOO Atlassian Bamboo is a continuous integration (CI) and deployment server. Bamboo assists software 51 development teams by providing automated Customer references from happy building and testing of software source-code Atlassian Bamboo users status, updates on successful and failed builds and reporting tools for statistical analysis. VIEW ALL REFERENCES "With Git and Bitbucket, we’re able to complete 3x as many code reviews, which ultimately results in fewer bugs, fewer support tickets, and better software." Kurt Chase Director of Release Engineering, Splunk "We love Hipchat’s screen-sharing and video chat capability. With one screen-sharing session alone, we’re spared at least 20 email exchanges." Corey Merkel Software Developer, OGSystems “Atlassian support and project management tools allow us to rapidly develop, deploy, and support software for our customers. We save time and effort, which is critical for us as a small business. In doing so, we're able to deliver great products and support to our customers who are working on finding cures for serious diseases." Andy Fleming Founder and Lead Developer, Halogenics "Bitbucket takes a lot of uncertainty out of the development process, and it really adds a lot to the quality of the software we’re developing." Paul Dunham Principal Application Developer, TriNet 9 TRUSTED BY ABOUT CHEF Chef is the leader in web-scale IT automation. It 134 gives us a model for automating IT infrastructure and applications that drive self-reliance across Customer references development and operations teams and helping from happy Chef users businesses become faster, safer and more flexible. VIEW ALL REFERENCES "With Chef, we can sleep well knowing our services are always configured and running exactly as needed, without needing to spend hundreds of thousands to do it ourselves." Jeremy Przygode CEO, Stratalux "With Chef we are in a better position to scale our organization quickly, which allows us to offer our customers reliable access to our popular social games. Getting on board with Chef was one of the best things that we did." Shadow Roldan Director of Technical Operations, iWin "Chef allows us to do in minutes what used to take a day or more, it’s just that easy to work with. You write some simple code, then reuse again and again. This not only makes life a lot easier, but also makes our infrastructure error-proof, as there’s no risk of potential human error." Ashley Streb Vice President of Technology, Brightcove “We can push a button and have a completely new VPC, with new application stacks, operational in less than 10 minutes. It has created a highly resilient ecosystem in which we’ve had zero data loss in five years.” Robert Morrish Chief Technology Officer, Haventec 10 TRUSTED BY ABOUT CLOUDBEES CloudBees is the hub of enterprise Jenkins and DevOps, providing companies with smarter solutions for automating 198 software development and delivery. CloudBees starts with Jenkins, the most trusted and widely-adopted continuous Customer references from delivery platform, and adds enterprise-grade security, happy CloudBees users scalability, manageability and expert-level support. By making the software delivery process more productive, manageable and hassle-free, CloudBees puts companies on VIEW ALL REFERENCES the fastest path to transforming great ideas into great software and returning value to the business more quickly. "The CloudBees Platform is helping us achieve our goals to open source our code by making it easier for developers to contribute, give rapid feedback on pull requests, provide the current status of projects and support low cost public builds. This spurs an increased pace of innovation that benefits not only Netflix and our customers, but the entire… Gareth Bowles Senior Tools Engineer, Netflix "High availability and frequent upgrades are vital to our business, so we need to deliver updates without maintenance windows. This sounds simple, but it is difficult to implement,
Recommended publications
  • Modisco: a Model Driven Reverse Engineering Framework Hugo Bruneliere, Jordi Cabot, Grégoire Dupé, Frédéric Madiot

    Modisco: a Model Driven Reverse Engineering Framework Hugo Bruneliere, Jordi Cabot, Grégoire Dupé, Frédéric Madiot

    MoDisco: a Model Driven Reverse Engineering Framework Hugo Bruneliere, Jordi Cabot, Grégoire Dupé, Frédéric Madiot To cite this version: Hugo Bruneliere, Jordi Cabot, Grégoire Dupé, Frédéric Madiot. MoDisco: a Model Driven Reverse Engineering Framework. Information and Software Technology, Elsevier, 2014, 56 (8), pp.1012-1032. 10.1016/j.infsof.2014.04.007. hal-00972632 HAL Id: hal-00972632 https://hal.inria.fr/hal-00972632 Submitted on 7 Apr 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. MoDisco: a Model Driven Reverse Engineering Framework Hugo Bruneli`erea,1,∗, Jordi Cabota, Gr´egoire Dup´eb, Fr´ed´eric Madiotc aAtlanMod (Inria & LINA), Ecole des Mines de Nantes, 4 rue Alfred Kastler, 44307 Nantes, France bMia-Software, 4 rue du Chateau de l’Eraudi`ere, 44324 Nantes, France cObeo, 7 boulevard Amp`ere, Espace Performance La Fleuriaye, 44481 Carquefou, France Abstract Context: Most companies, independently of their size and activity type, are facing the problem of managing, maintaining and/or replacing (part of) their existing software systems. These legacy systems are often large applications playing a critical role in the company’s information system and with a non-negligible impact on its daily operations.
  • Rugby - a Process Model for Continuous Software Engineering

    Rugby - a Process Model for Continuous Software Engineering

    INSTITUT FUR¨ INFORMATIK DER TECHNISCHEN UNIVERSITAT¨ MUNCHEN¨ Forschungs- und Lehreinheit I Angewandte Softwaretechnik Rugby - A Process Model for Continuous Software Engineering Stephan Tobias Krusche Vollstandiger¨ Abdruck der von der Fakultat¨ fur¨ Informatik der Technischen Universitat¨ Munchen¨ zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr. Helmut Seidl Prufer¨ der Dissertation: 1. Univ.-Prof. Bernd Brugge,¨ Ph.D. 2. Prof. Dr. Jurgen¨ Borstler,¨ Blekinge Institute of Technology, Karlskrona, Schweden Die Dissertation wurde am 28.01.2016 bei der Technischen Universitat¨ Munchen¨ eingereicht und durch die Fakultat¨ fur¨ Informatik am 29.02.2016 angenommen. Abstract Software is developed in increasingly dynamic environments. Organizations need the capability to deal with uncertainty and to react to unexpected changes in require- ments and technologies. Agile methods already improve the flexibility towards changes and with the emergence of continuous delivery, regular feedback loops have become possible. The abilities to maintain high code quality through reviews, to regularly re- lease software, and to collect and prioritize user feedback, are necessary for con- tinuous software engineering. However, there exists no uniform process model that handles the increasing number of reviews, releases and feedback reports. In this dissertation, we describe Rugby, a process model for continuous software en- gineering that is based on a meta model, which treats development activities as parallel workflows and which allows tailoring, customization and extension. Rugby includes a change model and treats changes as events that activate workflows. It integrates re- view management, release management, and feedback management as workflows. As a consequence, Rugby handles the increasing number of reviews, releases and feedback and at the same time decreases their size and effort.
  • Enterprise Architecture

    Enterprise Architecture

    Enterprise Architecture Dr. Adnan Albar Faculty of Computing & Information Technology King AbdulAziz University - Jeddah 1 Enterprise Architecture Methods Lecture 5 Week 5 Slides King AbdulAziz University - FCIT 2 Overview . Description Languages for Business & IT Domains . IDEF . BPMN . Testbed . ARIS . Unified Modeling Language . Service-Oriented Architecture (SOA) Slide 3 Description Languages . In domains such as business process design and software development, we find established description languages for modeling these domains. For software modeling, UML is of course, the single dominant language. In organization and process modeling, on the other hand, a multitude of languages are in use: there is no standard for models in this domain. We will focus on languages that either find widespread use or have properties that are interesting from the perspective of our goals in developing an enterprise architecture language. Slide 4 IDEF – Integrated DEFinition Methods .IDEF is a family of languages .Used to perform enterprise modeling and analysis .Currently, there are 16 IDEF methods. Of these methods, IDEF0, IDEF3, and IDEF1X (‘the core’) are the most commonly used. Slide 5 IDEF – The Scope it Covers .Functional modeling, IDEF0: The idea behind IDEF0 is to model the elements controlling the execution of a function, the actors performing the function, the objects or data consumed and produced by the function, and the relationships between business functions (shared resources and dependencies). .Process modeling, IDEF3: IDEF3 captures the workflow of a business process via process flow diagrams. These show the task sequence for processes performed by the organization, the decision logic, describe different scenarios for performing the same business functions, and enable the analysis and improvement of the workflow.
  • D1.1.1 Public State of the Art Document

    D1.1.1 Public State of the Art Document

    D1.1.1 Public state of the art document Programme ITEA3 Challenge Smart Engineering Project number 17038 Project name Visual diagnosis for DevOps software development Project duration 1st October 2018 – 30st June 2022 Project website Project WP WP1 - Pre-studies and requirements Project Task Task 1.1 – Update of state-of-art and state-of-the practice analysis for visualization in software projects in DevOps context Deliverable type X Doc Textual deliverable SW Software deliverable Version V17 Delivered 18/11/2019 Access x Public Abstracts are public Confidential D1.1.1 Public state of the art document Document Contributors Partber Author Role EXPERIS Ester Sancho editor EXPERIS Miriam Moreno writer GRO Paris Avgeriou writer INVENCO Mika Koivuluoma writer OCE Lou Somers writer/reviewer OULU Markus Kelanti writer TAU Kari Systä writer/reviewer TAU Outi Sievi-Korte writer/reviewer TIOBE Paul Jansen writer TIOBE Marvin Wener writer UPC Lidia López writer UPC Xavier Franch writer VINCIT Veli-Pekka Eloranta writer Document History Date Version Editors Status 18/06/2019 ToC EXPERIS Table of Content 10/07/2019 V01 TAU Draft 30/09/2019 V02 OCE/GRO Draft 17/10/2019 V06 TIOBE Draft 22/10/2019 V08 OULU Draft 12/11/2019 V09 VINCIT 1ST Final Draft 20/11/2019 V10 OCE Reviewed version 26/11/2019 V12 UPC/EXPERIS/TAU 2nd Final Draft 10/12/2019 V16 EXPERIS Final Version 16/12/2019 V16.01 TAU Peer Review 18/12/2019 V17 EXPERIS Submission 2 D1.1.1 Public state of the art document Table of Contents Executive Summary ............................................................................................................................. 6 1.
  • Magic Quadrant for Application Release Automation

    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.
  • CI-CD-For-Infrastructure-Configuration

    CI-CD-For-Infrastructure-Configuration

    Abstract & Overview Organizations of all sizes, from the leanest startup to the stodgiest enterprise, use CI/CD practices to greatly improve production and delivery of software. This yields higher- quality software at a lower cost and allows businesses to deliver ideas to market faster. As development teams adopt CI/CD practices, they start delivering new applications and releases faster and faster. This constantly changing software inevitably requires changes to infrastructure and configuration, but many operations teams aren’t accustomed to the pace—nor do they have the proper tools required. Trying to directly apply successful CI/CD practices for applications is highly unlikely to yield success for infrastructure and configuration changes. In this guide, we explore: • How and why CI/CD has been so successful for application changes • Infrastructure and configuration changes as a new bottleneck • Challenges with CI/CD for infrastructure and configuration changes • How to overcome challenges and implement CI/CD for infrastructure We include a hands-on guide for how to implement this with BuildMaster and Otter. You can do everything in this guide with BuildMaster Free and Otter Free editions! About Inedo, Otter, and BuildMaster We help organizations make the most of their Windows technology and infrastructure through our Windows-native and cross-platform DevOps tools. • BuildMaster, a tool designed to implement CI/CD, automates application releases. • Otter manages infrastructure. Harnessing the power of both tools allows users to manage infrastructure while enjoying all the benefits of CI/CD. Page 1 of 31 Page 2 of 31 Contents CI/CD for Applications: A Quick Refresher ................................................................................................................................................. 4 Pipelines: The Heart of CI/CD ....................................................................................................................................................................
  • Development and Deployment at Facebook

    Development and Deployment at Facebook

    Development and Deployment at Facebook Dror G. Feitelson Eitan Frachtenberg Kent L. Beck Hebrew University Facebook Facebook Abstract More than one billion users log in to Facebook at least once a month to connect and share content with each other. Among other activities, these users upload over 2.5 billion content items every day. In this article we describe the development and deployment of the software that supports all this activity, focusing on the site’s primary codebase for the Web front-end. Information on Facebook’s architecture and other software components is available elsewhere. Keywords D.2.10.i Rapid prototyping; D.2.18 Software Engineering Process; D.2.19 Software Quality/SQA; D.2.2.c Distributed/Internet based software engineering tools and techniques; D.2.5.r Testing tools; D.2.7.e Evolving Internet applications. Facebook’s main development characteristics are speed and growth. The front-end is under continuous development by hundreds of software engineers. These engineers commit code to the version control system up to 500 times a day, recording changes in some 3,000 files. Naturally, codebase size unique developers by week commits per month 14 800 10 700 12 600 10 8 500 8 6 400 6 300 4 4 200 LoC [millions] 2 100 2 active developers 0 0 0 ’05 ’06 ’07 ’08 ’09 ’10 ’11 ’12 ’05 ’06 ’07 ’08 ’09 ’10 ’11 ’12 number of commits [1000s] ’05 ’06 ’07 ’08 ’09 ’10 ’11 ’12 Figure 1: Different aspects of Facebook growth: growth of the number of engineers working on the code, growth in the total activity of these engineers, and growth of the codebase itself.
  • Release Engineering Processes, Models, and Metrics

    Release Engineering Processes, Models, and Metrics

    Release Engineering Processes, Models, and Metrics Hyrum K. Wright Empirical Software Engineering Laboratory Department of Electrical and Computer Engineering The University of Texas at Austin Austin, Texas 78712 [email protected] ABSTRACT The primary goal of this research is to develop techniques, No matter the development process or methodology, a soft- methods, metrics and processes whereby the release engi- ware product must ultimately be released to a user in a neering process can be quantitatively measured, reasoned readily consumable form. Different software products, from about, and improved. Such techniques will benefit the soft- desktop applications to web services, may require different ware industry by reducing release process overhead, and im- release processes, but each process must produce an arti- proving the quality of the release artifact. This paper gives fact which meets an expected level of quality, and is rela- a brief background of release engineering as a practice, the tively bug-free. We describe current research to model and existing research in this area, and how we intend to proceed quantify existing release processes, and an effort to prescribe toward our goals. improvements to those processes. 2. BACKGROUND Categories and Subject Descriptors Release engineering is the part of the software engineer- ing process during which the release artifact, usually an ex- D.2.9 [Software Engineering]: Management|software pro- ecutable, installer, library or source code package, is pro- cess models; D.2.7 [Software Engineering]: Distribution, duced. In traditional software development methodologies, Maintenance, Enhancement|release creation and distribu- such as the spiral or waterfall models, release engineering tion comes as part of the deployment and maintenance phases [1, 8].
  • Synechron Technology

    Synechron Technology

    Technology Practice overview www.synechron.com Unlike other firms, Synechron’s excellence - to drive transformative Our Value “Power of 3” approach and solutions. We have the unique ability proposition financial services expertise gives to provide an end-to-end approach, About Synechron us a competitive edge to tackle our from business consulting through clients’ problems from any vantage technical development to digital A unique approach to market point with great depth. Synechron enhancement. This empowers us combines the “Power of 3” - business to deliver solutions to some of the differentiation in the financial Accelerating Digital for process knowledge, digital design toughest business challenges. services domain and core technology delivery Banks, Asset Managers, and Insurance companies. Synechron is a leading Digital Consulting firm and is working to Accelerate Digital initiatives for banks, asset managers, and insurance Technology Digital companies around the world. • Technology Consulting • Experience Design We achieve this by providing our clients with innovative solutions • Application Development • Deployment and DevOps that solve their most complex business challenges and combining • Automation • Emerging Technology Synechron’s unique, end-to-end Digital, Business Consulting, and • Enterprise Architecture & Cloud Frameworks Technology services. Based in New York, the company has 18 offices • Quality Assurance • Blockchain COE around the globe, with over 8,000 employees producing over $500M+ • Systems Integration • AI Automation
  • Who Needs Release and Devops Engineers, and Why?

    Who Needs Release and Devops Engineers, and Why?

    Who Needs Release and DevOps Engineers, and Why? Noureddine Kerzazi Bram Adams ENSIAS, Mohammed V University in Rabat MCIS, Polytechnique Montreal [email protected] [email protected] ABSTRACT role overseeing and planning the transfer of deliverables to- The recent surge in interest in continuous delivery has opened wards the production environment? Penners et al. [7] found up the job market for release and DevOps engineers. How- that the experts consulted by them did not share a unique ever, despite an increasing number of conferences and publi- interpretation of the DevOps and release engineering roles, cations on continuous delivery, smaller companies and start- while Bass et al. [4] even define DevOps in terms of release ups still have a hard time determining the core tasks their engineering, i.e., \DevOps is a set of practices intended to future release and DevOps engineers should be responsible reduce the time between committing a change to a system for (and what the differences between those two roles are), and the change being placed into normal production, while while universities are not sure what essential techniques and ensuring high quality." skills they should teach to their students. This paper per- The Capability Maturity Model Integration (CMMI) de- forms an empirical analysis of online job postings to deter- scribes Release Management as emphasizing the Product In- mine and compare the main tasks of release and DevOps tegration (PI) process area [12]. The purpose of PI is to as- engineers, globally and across countries. Our qualitative semble the product from product components, to ensure that analysis shows that automation is the most important ac- the integrated product works properly, then to deliver it.
  • Continuous Delivery

    Continuous Delivery

    DZONE RESEARCH PRESENTS 2014 GUIDE TO CONTINUOUS DELIVERY BROUGHT TO YOU IN PARTNERSHIP WITH dzone.com/research/continuousdelivery © DZONE, INC. 2014 WELCOME TABLE OF CONTENTS Dear Reader, SUMMARY & HIGHLIGHTS 3 In recent years, we have grown accustomed to a KEY RESEARCH FINDINGS 4 constant stream of information that has fueled our news feeds, flooded our inboxes, and triggered INTRODUCING: CONTINUOUS DELIVERY constant notifications... and in all of the noise, BY STEVE SMITH 6 something has been lost. Clarity, concision, and relevance have become innocent bystanders in an CONTINUOUS DELIVERY PITFALLS age of information overload. While it is true the BY J. PauL REED 10 task of gathering information has become easier, finding the right information, when and where you THE CONTINUOUS DELIVERY need it, has become increasingly complex and, at TOOLCHAIN times, overwhelming. BY MattHEW SKELtoN 14 The guide you hold in your hands (or on your CONTINUOUS DELIVERY VISUALIZED 16 device) is a vital part of DZone’s fight against this growing trend. We recognize that as a technology INFRASTRUCTURE AS CODE: WHEN professional, having actionable knowledge at AUTOMATION ISN’t ENOUGH 22 your fingertips is a necessity. Your business BY MitcH PRONSCHINSKE challenges will not be put on hold while you try to identify the right questions to ask and sort CONTINUOUS DELIVERY MATURITY CHECKLIST 24 through endless information. In publishing our 2014 Guide to Continuous Delivery, we have worked SOLUTION DIRECTORY 25 hard to curate and aggregate a wealth of useful topic knowledge and insight into a concise and informative publication. While this is only our second publication of this CREDITS nature, we have come a long way so far and we have big plans for the future.
  • Methodology Project Release Processes Overview References

    Methodology Project Release Processes Overview References

    Release Engineering Processes in Open Source Projects Hyrum K. Wright and Dewayne E. Perry Emperical Software Engineering Laboratory Department of Electrical and Computer Engineering The University of Texas at Austin {hwright,perry}@ece.utexas.edu Overview Project Release Processes Methodology elease engineering is the part of the software engineering GCC release process e have begun a qualitative study the evolution of the re- Linux pre-2.6 release process process during which the release artifact, usually an exe- ... lease process for three specific open source projects: the R 4.2.0 4.2.1 4.2.2 4.2.3 4.2.4 4.3.0 W ... ... cutable, installer, or source code package, is produced. In tradi- 2.5.0 2.5.1 Linux Kernel; the Subversion version control system; and the 2.3.0 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7 2.3.75 tional software development methodologies, such as the spiral Gnu Compiler Collection (GCC). Each project organization has or waterfall models, release engineering comes as part of the re- ... ... significantly changed the release management process during 4.2 branchedStage 1 Stage 2 Stage 3 4.3 branchedStage 1 lease and maintenance phases. In recent years, commercial and ... ... their history, allowing us to study how process changes affected 2.2.0 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.28 2.4.0 open source software projects have begun to employ dedicated 2.4.1 the release artifact.