DOCSLIB.ORG

IBM Rational Clearcase to Perforce VCS Migration Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Rational Clearcase to Perforce VCS Migration Guide MIGRATION GUIDE IBM Rational ClearCase to Perforce VCS Migration Guide v2.5, January 31, 2017 This document provides information for planning a migration from a legacy ClearCase VCS system to Perforce VCS. Basic familiarity with ClearCase architecture, concepts, and terminology are helpful, but not strictly necessary, when reading this document. Corresponding Perforce concepts and terminology are introduced. We discuss preliminary planning and review three history import strategies – starting over, detailed history import (DHI), and baseline & branch import (BBI). ClearCase to Perforce migration projects vary greatly in scale and complexity. Small, simple environments with basic migration requirements are typically migrated in about eight business days, including Perforce setup, migration, and training for users and administrators. Large, complex ClearCase environments may perform a series of migrations that occur over the course of a several months or more, as teams migrate at times convenient for them. This document is not intended to be a replacement for an actual assessment of your environment. An assessment would focus on those factors most relevant to your environment and produce a custom migration strategy. MIGRATION GUIDE IBM Rational ClearCase to Perforce SCM Migration Guide | ii 1. Introduction .......................................................................................................................................1 2. Preliminary Migration Preparation.................................................................................................1 2.1. Review Existing Branching Strategy ......................................................................................1 2.2. Perforce Directory Standard (PDS) ........................................................................................1 2.3. Release Processes and the PDS .............................................................................................1 2.4. Perforce Streams .....................................................................................................................2 2.5. Addressing Intellectual Property Concerns .........................................................................2 2.6. Training .....................................................................................................................................2 2.7. Perforce Transition Team ........................................................................................................2 3. Import Strategies ..............................................................................................................................3 3.1. Tips – Starting Over .................................................................................................................3 3.1.1. Starting Over – Pros .......................................................................................................3 3.1.2. Starting Over – Cons ......................................................................................................3 3.2. Detailed History Import ..........................................................................................................3 3.2.1. ClearCase Detailed Import History Preparation ........................................................4 3.2.2. Custom Scripting ...........................................................................................................4 3.2.3. Hardware Capacity Planning ........................................................................................4 3.2.4. Detailed History Import – Pros ......................................................................................4 3.2.5. Detailed History Import – Cons ....................................................................................5 3.3. Baseline & Branch Import .......................................................................................................5 3.3.1. Baseline & Branch Import – Pros ..................................................................................6 3.3.2. Baseline & Branch Import – Cons .................................................................................7 3.3.3. Warnings .........................................................................................................................7 4. Terminology and Concepts .............................................................................................................7 4.1. VOBs and Depots ....................................................................................................................7 4.2. ClearCase Regions ..................................................................................................................7 4.3. VOB Servers vs. “The Server” .................................................................................................8 4.3.1. Operating System Selection .........................................................................................8 4.4. Registry and License Servers .................................................................................................8 4.5. Release Servers and Installation ............................................................................................8 4.6. View Servers, Protecting Unversioned and Checked Out Files .........................................9 4.7. ClearCase MultiSite vs. Perforce Proxies ..............................................................................9 4.8. Replacing ClearCase Views with Perforce Workspaces ......................................................9 4.9. Rethink Label Strategies .......................................................................................................10 4.10. Unified Change Management (UCM) ...............................................................................10 4.11. Migration Technical Details ................................................................................................10 4.11.1. Evil Twins .....................................................................................................................10 4.11.2. Symlinks on Windows ...............................................................................................11 4.11.3. File Type Mappings and Limitations .......................................................................11 Perforce Software 400 N. 1st Avenue, Suite 200 +1 510.864.7400 www.perforce.com Minneapolis, MN 55401 [email protected] Copyright © 2008-2017, Perforce Software. All rights reserved. MIGRATION GUIDE IBM Rational ClearCase to Perforce SCM Migration Guide | 1 • Helps convey branching patterns for 1. Introduction everything Perforce. This document provides information for planning a • Helps intuitively map change propagation paths for the migration from a legacy ClearCase VCS system to Perforce various flows of change (e.g. the life of a bug discovered VCS. Basic familiarity with ClearCase architecture, in maintenance, or the life of a new feature). concepts, and terminology are helpful, but not strictly • Conveys the stage in the life cycle of any particular necessary, when reading this document. Corresponding piece of code: experimental, development, released. Perforce concepts and terminology are introduced. It is a best practice to establish a Perforce Directory Standard We discuss preliminary planning and review three history (PDS) to establish the directory structure and corresponding import strategies – starting over, detailed history import branching strategy in Perforce. A template for developing (DHI), and baseline & branch import (BBI). your own PDS is available for download here. You can participate in discussions about the PDS on the Perforce ClearCase to Perforce migration projects vary greatly in scale Forums here. Contact Perforce Consulting and complexity. Small, simple environments with basic ([email protected]) for further information. migration requirements are typically migrated in about eight business days, including Perforce setup, migration, 2.3. Release Processes and the PDS and training for users and administrators. Large, complex The directory structure in Perforce can be thought of as ClearCase environments may perform a series of migrations “low” and “high” levels. Low levels represent your software that occur over the course of a several months or more, as products, and can vary for each software product. High teams migrate at times convenient for them. levels of a Perforce directory structure convey branching structure, project management, and software lifecycle This document is not intended to be a replacement for an information. A well-designed, high-level directory structure actual assessment of your environment. An assessment is intuitive for developers and lends itself well to project would focus on those factors most relevant to your management metrics, policy enforcement by branch type, environment and produce a custom migration strategy. and automation of various kinds. Migration to Perforce typically involves defining a Perforce 2. Preliminary Migration Preparation Directory Standard (PDS) for each product imported into Perforce, and in some cases for the entire organization. A 2.1. Review Existing Branching Strategy Early in migration planning, determine whether the current PDS encourages consistency in release processes for various branching strategy used in ClearCase, if any, is appropriate software products, but can be as flexible as needed to to use going forward with Perforce. If
Load more

Recommended publications
  • Ansys SCADE Lifecycle®
    EMBEDDED SOFTWARE Ansys SCADE LifeCycle® SCADE LifeCycle is part of the Ansys Embedded Software family of products and solutions that includes modules providing unique support for application lifecycle management. This product line features requirements traceability via Application Lifecycle Management (ALM) tools, traceability from models, configuration and change management, and automatic documentation generation. SCADE LifeCycle enhances the functionalities of Ansys SCADE® tools with add-on modules that bridge SCADE solutions and Requirement Management tools or PLM/ALM (Product Lifecycle Management/ Application Lifecycle Management) tools. With SCADE LifeCycle, all systems and software teams involved in critical applications development can manage and control their design and verification activities across the full life cycle of their SCADE applications. / Requirements Traceability SCADE LifeCycle Application Lifecycle Management (ALM) Gateway provides an integrated traceability analysis solution for safety-critical design processes with SCADE Architect, SCADE Suite, SCADE Display, SCADE Solutions for ARINC 661 and SCADE Test: • Connection to ALM tools: linkage to DOORS NG, DOORS (9.6 and up) Jama Connect, Siemens Polarion, Dassault Systèmes Reqtify 2016. • Graphical creation of traceability links between requirements or other structured documents and SCADE models. • Traceability of test cases from SCADE Test Environment projects. • Bidirectional navigation across requirements and tests. • Customizable Export of SCADE artifacts to DOORS or Jama Connect. • Compliant with DO-178B, DO-178C, EN 50128, IEC 61508, ISO 26262, and IEC 60880 standards. EMBEDDED SOFTWARE / SCADE LifeCycle® // 1 / Project Documentation Generation SCADE LifeCycle Reporter automates the time-consuming creation of detailed and complete reports from SCADE Suite, SCADE Display, SCADE Architect and SCADE UA Page Creator for ARINC 661 designs through: • Generation of reports in RTF or HTML formats.
    [Show full text]
  • Configuration Management for Distributed Development
    Software Configuration Management Configuration Management for Distributed Development By Nina Rajkumar. © Think Business Networks Pvt. Ltd., July 2001 All rights reserved. You may make one attributed copy of this material for your own personal use. For additional information or assistance please contact Nina at (+91)422-320-606. www.thinkbn.com • 697A, Trichy Road, Coimbatore, TN 641045. Table of Contents Configuration Management for Distributed Development.............................. 4 Configuration Management ................................................................................ 5 Distributed Development.................................................................................... 5 Cases of Distributed Development ..................................................................... 6 Distance Working ........................................................................................... 6 Outsourcing..................................................................................................... 6 Co-located Groups .......................................................................................... 7 Distributed Groups.......................................................................................... 7 Architecture ........................................................................................................ 8 Remote Login.................................................................................................. 8 Several sites by Master-Slave connections ....................................................
    [Show full text]
  • 85 Attachment 1 –Organizational Chart
    Contract No. 071B3200143 Attachment 1 –Organizational Chart 85 Contract No. 071B3200143 Appendix A - Breakdown of Hardware and Related Software Table 1: Hardware Cost ($): State Brand, Model # Item Specifications will provide from Comments and Description existing Contracts Total # of Virtual The hardware is Machines: 48 sized for Production, QA/Staging, Secure-24 VMware Total # of Virtual Development, and Cluster Access for CPUs: 96 Sandbox Server deploying ISIM, environments in the ISAM and ISFIM Total Virtual RAM: primary data center components 416 GB and for Production, and QA environments in the OS: RedHat Linux secondary data 6.x center The total storage is estimated for Total Storage: 35.7 Production, , TB QA/Staging, Development and Enterprise Class Sandbox Storage (3.8TB of Bronze SAN Storage Tier, 15.8TB of environments in the Silver Tier, 5.1TB of primary data center Logs Tier, 11TB of and for Production, Gold Tier) QA environments in the secondary data center CD/DVD Backup Device None None Rack w/ Power Supply Rack mountable Redundant Power Screen None None A total of 10 Web Gateway appliances are estimated for Production, QA/Staging, Web Gateway Development and Any other Hardware (list) v7.0 Hardware Appliance Sandbox environments in the primary data center and for Production, QA environments in the secondary data center. TOTAL $ 86 Contract No. 071B3200143 Table 2: Related Software Software Component Product Name Cost ($): State # of Licenses Comments License and Version will provide from existing Contracts Contractor user laptops already include this software. We will reuse the Report writers MS Office 2010 State owned software State of Michigan user licenses laptops will need this software for up to 4 users.
    [Show full text]
  • Using Visual COBOL in Modern Application Development Micro Focus the Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK
    Using Visual COBOL in Modern Application Development Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com © Copyright 2018-2020 Micro Focus or one of its affiliates. MICRO FOCUS, the Micro Focus logo and Visual COBOL are trademarks or registered trademarks of Micro Focus or one of its affiliates. All other marks are the property of their respective owners. 2020-08-25 ii Contents Using Visual COBOL in Modern Application Development ........................... 4 Introduction to Modern Application Development ................................................................4 What is Modern Application Development? ..............................................................4 Key Concepts in Modern Application Development ..................................................5 Steps Involved in Modern Application Development ................................................ 6 Agile Methods ..................................................................................................................... 7 Introduction to Agile Methods ...................................................................................7 Agile Development Workflow ....................................................................................7 Agile Development and Micro Focus Development Tools .........................................9 Continuous Integration ...................................................................................................... 11 Introduction to Continuous Integration ..................................................................
    [Show full text]
  • Revision Control Solutions to Protect Your Documents and Track Workflow
    Revision Control Solutions to Protect Your Documents and Track Workflow WHITE PAPER Contents Overview 3 Common Revision Control Systems 4 Revision Control Systems 4 Using BarTender with Revision Control Systems 4 Limitations of Windows Security 5 Librarian 6 Librarian Features 6 Benefits of Using Librarian with BarTender 7 File States, Publishing and Workflow in Librarian 8 Don’t Forget About Security! 9 Related Documentation 10 Overview A revision control system is based around the concept of tracking changes that happen within directories or files, and preventing one user from overwriting the work of another. Some revision control systems are also used to establish and track workflow for the progression of a file through a series of states. The collection of files or directories in a revision control system are usually called a repository. These systems allow you to specify a directory, file or group of files that will have their changes tracked. This frequently entails users "checking out" and "checking in" files from a repository. Changes are tracked as the user edits the folder or file; these changes will be visible to all users once the item is checked back in. Each revision is annotated with a timestamp and the person making the change. Some of the benefits of revision control include: l Automatic revision numbering for easy tracking. l Enhanced security. Not only does a "check in" and "check out" system keep one user's work from overwriting another, it can prevent unauthorized or even malicious users from accessing a document. l Some revision control systems include publishing "states," which allow you to track the publishing progress of a document and establish a logical, traceable workflow.
    [Show full text]
  • Main Brochure2.Indd
    Automate your Build Process . Powerful and fl exible user interface . Automate version control, compilers, install builders, deployment, testing, notifi cations, and lots more... Dynamic build process using fl ow control, iterators, loops, and exceptions . Full debugger built in - breakpoints, variable watches, live logging . Script events for every action to customise your build process Hierarchical Logging Error Handling FinalBuilder ActionStudio . The log is presented in the same . Easily detect and handle errors during . Allows development of native FinalBuilder hierarchy as your build process your build process actions . Optionally view live log output . Exception handling actions . Includes property page designer and as the build runs include: TRY, CATCH, FINALLY code editor with syntax highlighting . Builds logs are automatically . Control the fl ow of your build process . Develop actions in VBScript, JScript, COM, archived and recover from errors or any .Net language such as C#, VB.Net or Delphi for .Net . Export the log as XML, HTML, or . Unhandled errors trigger the OnFailure Text action list . Included in all editions of FinalBuilder VSoft Technologies Pty Ltd http://www.fi nalbuilder.com ABN: 82 078 466 092 P.O. Box 126, Erindale Centre, ACT 2903, Australia salesinfo@fi nalbuilder.com Phone: +61 2 6282 7488, Fax +61 2 6282 7588 news://news.fi nalbuilder.com FinalBuilder Integrates with your version control system . Microsoft TeamSystem Use a GUI instead of XML fi les . Microsoft Visual SourceSafe . Perforce Although FinalBuilder uses an XML based fi le format, you . IBM Rational ClearCase don’t need to understand it or even look at it. The FinalBuilder . QSC Team Coherence GUI allows you to quickly and easily create a build process .
    [Show full text]
  • Why Devops Stops
    1 What is Krista? Intelligent Automation Deployment is Simple Krista is a modern conversational Intelligent Krista's Natural Language Processing supports Automation platform designed to easily leverage voice, text, and *bots to deliver automation anyone existing IT assets. Krista's unique informal understands. By utilizing existing communication approach enables business process owners to methods in conversations, you take advantage of quickly build new lookup or data entry workflows how your employees already communicate. Krista without waiting in line for expensive IT or quickly deploys to existing desktops, mobile development resources. Krista uses a unique phones, Slack, and web browsers that your programming method similar to a text conversation employees are already using. You won't need to between one or more people. By following the way train employees or maintain brittle documentation humans already communicate, Krista enables since the automation follows existing voice and anyone to build and create workflows around texting conversations similar to WhatsApp or business process constraints. The conversational Facebook Messenger. If your employees can text, workflows eliminate maintenance and upkeep they can interact with numerous systems to required from traditional record and playback support customers, consume enterprise services, automation tools. Krista's conversations are deploy IT changes, or update important KPIs. beautifully simple, with enough power, scale, and security to find any answer inside the largest enterprises. DevOps – It’s improving. DevOps Evolution Model Stage 1 Stage 2 Stage 3 Stage 4 Stage 5 Automated infrastructure Normalization Standardization Expansion Self-service delivery Many DevOps initiatives and cultures slow or stop at Stage 3 and fail to scale since organizational structures (aka people) become constraints in the Neutral Zone.
    [Show full text]
  • Git for the ASP.NET Programmer
    git for the ASP.NET Programmer Paul Litwin Fred Hutchinson Cancer Research Center [email protected] @plitwin Slides & samples can be found here… • http://tinyurl.com/DevInt2015Oct Litwin Git for the ASP.NET Programmer 2 Session Itinerary • Why distributed version control? • git basics • Command line git • Using git from VS Code • Using git from Visual Studio • Branching and merging • Wrap up Litwin Git for the ASP.NET Programmer 3 Why distributed version control? Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency Created by Linux creator, Linus Torvalds Litwin Git for the ASP.NET Programmer 5 The name git? “I'm an egotistical bastard, and I name all my projects after myself. First Linux, now git.” Linus Torvalds quote from 2007 Litwin Git for the ASP.NET Programmer 6 Centralized Version Control One repository using a client-server model Litwin Git for the ASP.NET Programmer 7 Distributed Version Control Many repositories using peer to peer model Litwin Git for the ASP.NET Programmer 8 Comparing centralized (tfs) vs distributed (git) Attribute Centralized Distributed TFS, SVN, PVCS git, Mercurial Repositories 1 Many Model Client-server Peer-to-peer Speed of common Slower Fast against local repo operations Redundancy of system None; single point of Redundancy built in failure Offline work More difficult Easy Merging of changes When you check When you sync changes changes in (push/pull) Litwin Git for the ASP.NET Programmer 9 git Basics
    [Show full text]
  • TIBCO Designer User's Guide
    TIBCO Designer™ User’s Guide Software Release 5.10 August 2015 Two-Second Advantage® Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO ActiveMatrix Service Gateway, TIBCO BusinessEvents, TIBCO BusinessConnect, and TIBCO BusinessConnect Trading Community Management are either registered trademarks or trademarks of TIBCO Software Inc.
    [Show full text]
  • Rational Tools Architect
    A Better Solution, Inc. abs-arc32 Rational Tools Architect Objective: Using over 15 years of CM experience to provide assistance with implementation of configuration management, process creation, and process creation and control through the use of the Rational toolset. Seek position to enhance the overall quality of software configuration and release control at the project, department or enterprise level. Provide implementation so departments could evolve to higher compliance states in order to develop their code more quickly and with less cost. Education: DeVry University of Technology – Bachelor of Arts in Computer Information Systems. Rational Certifications: IBM Certified Administrator Rational ClearQuest v2003, in 2008 Other Certs: Tasktop Certified Deployment Specialist Rational Tools Training: ClearQuest Administration in July 2002 & January 2005 ClearQuest MultiSite Administration in August 2002 ClearCase Administration in July 2002 ClearCase MultiSite Administration in November 2002 Related Skills: IBM Rational ClearCaseUCM & MultiSite Rational Team Concert IBM Rational RequistePro IBM Rational Manual Tester IBM Rational Functional Tester IBM Rational Software Architect IBM Rational Software Modeler IBM Rational Test Manager IBM Rational SoDA IBM Rational Unified Process IBM Rational DOORS Next Generation UrbanCode Release & UrbanCode Deploy Microsoft Visual Source Safe Microsoft Office Suite Microsoft Project Adobe Designer Premier CS3 Atlassian JIRA Subversion ANT PERL, VB Script, SQL Plus+, JAVA, HTML Rational Tools Experience: A Better Solution, Inc. – Atlanta, GA 2011 – Present RATIONAL TOOLS CONSULTANT Software Configuration Management: Consulting concentrating on CM practices and implementation using ClearCase, ClearCase with UCM, MultiSite, ClearQuest and Rational Team Concert. Design and implement process automation and simplification. Assist in Planning and migration of code bases to ClearCase from other CM tools.
    [Show full text]
  • Windows and CVS Suite
    Windows and CVS Suite INSTALL GUIDE 2009 Build 7799 April 2021 March Hare Software Ltd INSTALL GUIDE 2009 Build 7799 April 2021 Legal Notices Legal Notices There are various product or company names used herein that are the trademarks, service marks, or trade names of their respective owners, and March Hare Software Limited makes no claim of ownership to, nor intends to imply an endorsement of, such products or companies by their usage. This document and all information contained herein are the property of March Hare Software Limited, and may not be reproduced, disclosed, revealed, or used in any way without prior written consent of March Hare Software Limited. This document and the information contained herein are subject to confidentiality agreement, violation of which will subject the violator to all remedies and penalties provided by the law. LIMITED WARRANTY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, March Hare Software Limited AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, WITH REGARD TO THIS DOCUMENT, AND ANY ADVICE OR RECOMMENDATION CONTAINED IN THIS DOCUMENT. NO OTHER WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL March Hare Software Limited OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE FOLLOWING DOCUMENTATION INCLUDING ANY RECOMMENDATION OR ADVICE THERIN, EVEN IF March Hare Software Limtied HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Reference Architecture for Google Cloud's Anthos with Lenovo
    Reference Architecture for Google Cloud’s Anthos with Lenovo ThinkAgile VX Last update: 11 June 2020 Describes the business case Provides an overview of for modern micro-services, Google Kubernetes Engine containers, and multi-cloud (GKE) on-premises with Anthos Describes the architecture and Provides Anthos use-cases implementation of Anthos and examples including solution on ThinkAgile VX DevOps, Service management, hyperconverged infrastructure Hybrid and Multi-cloud Srihari Angaluri Xiaotong Jiang Markesha Parker Table of Contents 1 Introduction ............................................................................................... 1 2 Business problem and business value ................................................... 2 2.1 Business problem .................................................................................................... 2 2.2 Business Value ........................................................................................................ 3 3 Requirements ............................................................................................ 4 3.1 Introduction .............................................................................................................. 4 3.1.1 Modern application development ................................................................................................. 4 3.1.2 Containers ................................................................................................................................... 5 3.1.3 DevOps .......................................................................................................................................
    [Show full text]