Continuous Integration (CI) and Continuous Delivery (CD) : a practical guide to designing and developing pipelines /
Use continuous Integration (CI) and continuous delivery (CD) to improve the speed of software delivery. This book presents a game changer--how to use pipelines to automate the software delivery process. The theories about CI/CD are much the same, but the book covers what the development of pipelines...
Saved in:
| Main Author: | |
|---|---|
| Format: | Electronic eBook |
| Language: | English |
| Published: |
Berkeley, CA :
Apress L. P.,
2023.
|
| Subjects: | |
| Online Access: | CONNECT |
MARC
| LEADER | 00000cam a22000007a 4500 | ||
|---|---|---|---|
| 001 | in00006364468 | ||
| 006 | m o d | ||
| 007 | cr cnu|||||||| | ||
| 008 | 230401s2023 cau o 000 0 eng d | ||
| 005 | 20230428141111.8 | ||
| 019 | |a 1374424037 | ||
| 020 | |a 9781484292280 |q (electronic bk.) | ||
| 020 | |a 1484292286 |q (electronic bk.) | ||
| 020 | |z 1484292278 | ||
| 020 | |z 9781484292273 | ||
| 024 | 7 | |a 10.1007/978-1-4842-9228-0 |2 doi | |
| 035 | |a 1WRLDSHRon1374425561 | ||
| 035 | |a (OCoLC)1374425561 |z (OCoLC)1374424037 | ||
| 037 | |a 9781484292280 |b O'Reilly Media | ||
| 040 | |a EBLCP |b eng |c EBLCP |d ORMDA |d GW5XE |d YDX | ||
| 049 | |a TXMM | ||
| 050 | 4 | |a QA76.758 | |
| 082 | 0 | 4 | |a 005.1 |2 23/eng/20230404 |
| 100 | 1 | |a Merode, Henry van, |e author. | |
| 245 | 1 | 0 | |a Continuous Integration (CI) and Continuous Delivery (CD) : |b a practical guide to designing and developing pipelines / |c Henry van Merode. |
| 260 | |a Berkeley, CA : |b Apress L. P., |c 2023. | ||
| 300 | |a 1 online resource (429 p.) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 500 | |a Description based upon print version of record. | ||
| 505 | 0 | |a Intro -- Table of Contents -- About the Author -- About the Technical Reviewers -- Acknowledgments -- Chapter 1: The Pitfalls of CI/CD -- Challenges -- Oversimplified Diagrams and Misalignment -- Lack of Design Patterns -- Vulnerabilities -- Pipeline Testing -- Application Code vs. Infrastructure Code -- Organizing and Maintaining Pipelines -- Technical Constraints -- Legacy -- Summary -- Chapter 2: CI/CD Concepts -- Principles -- Positioning of CI/CD -- Application Lifecycle Management -- CI/CD Journey -- Naming Conventions -- Summary -- Chapter 3: Requirements Analysis -- Overview | |
| 505 | 8 | |a Way of Working -- Technology -- Information -- Security (General) -- Compliance and Auditability -- Resource Constraints -- Manageability -- Operations -- Quality Assurance -- Metrics -- Monitoring -- Sustainability -- Governance -- Summary -- Chapter 4: Pipeline Design -- Design -- CI/CD and Pipeline Design Approach -- BPMN 2.0 -- BPMN Elements Overview -- BPMN in Action -- Level of Detail -- Logical Design vs. Realization -- The Generic CI/CD Pipeline -- Validate Entry Criteria -- Execute Build -- Perform Unit Tests -- Analyze Code -- Package Artifact -- Publish Artifact | |
| 505 | 8 | |a Provision Test Environment -- Deploy Artifact to Test -- Perform Test -- Validate Infrastructure Compliance -- Validate Exit Criteria -- Perform Dual Control -- Provision Production Environment -- Deploy Artifact to Production -- Notify Actors -- Design Strategies -- Context Diagram -- Branching Strategy -- Trunk-Based Workflow -- Feature Branch Workflow -- Gitflow -- Build Strategy -- Vertical Scaling -- Full Builds vs. Incremental Builds -- Parallel Builds -- Pipeline Caching -- Build Targets -- Cross-Platform Builds -- Multiteam Build Strategy -- Test Strategy -- Automated vs. Manual Tests | |
| 505 | 8 | |a Functional vs. Nonfunctional Tests -- Parallel Execution vs. Sequential Execution -- Manual Tests Performed by Specialists -- Long Execution Time vs. Short Execution Time -- Release Strategy -- Road Map-Based Release -- Timeboxed Release -- Regular Release -- Continuous Deployment -- Feature Management-Based Release -- Production Deployment Strategy -- Re-create Deployment -- Blue/Green Deployment -- Rolling Update and Canary Deployment -- A/B Test Strategy -- Other Design Considerations -- Delegation -- Application Architecture -- Orchestration -- Event-Based CI/CD -- Resource Constraints | |
| 505 | 8 | |a Commercial Off the Shelf -- Summary -- Chapter 5: Pipeline Development -- Pipeline Specification -- Multibranch, Multistage Pipeline -- User Interface-Based Pipelines -- Scripted Pipelines -- Declarative Pipelines -- Constructs -- Triggers -- Execution Environment -- Connections -- Variables -- Conditions -- Caching -- Matrix -- Deployment Strategy -- Auto-cancel -- On Success/Failure -- Fail Fast -- Priority -- Test Shards -- Templates and Libraries -- Gates and Approvals -- Workflow -- Plugins and Marketplace Solutions -- Repositories: Everything as Code -- Third-Party Libraries and Containers | |
| 500 | |a Versioning and Tagging | ||
| 520 | |a Use continuous Integration (CI) and continuous delivery (CD) to improve the speed of software delivery. This book presents a game changer--how to use pipelines to automate the software delivery process. The theories about CI/CD are much the same, but the book covers what the development of pipelines looks like and how testing of pipelines themselves should be performed. Most teams just plunge into coding, without thinking about the CI/CD process itself. Why don't we use the same development method for pipelines that we use for apps? Pipelines code development undergoes similar stages as application code development, such as requirements analysis, development, testing, implementation, operations, and monitoring. This is the starting point of the book. It describes the current challenges with pipeline development and how this process can be improved and structured. It describes in detail how to design pipelines and shows examples in BPMN 2.0 notation. What You'll Learn Know the shortcomings and challenges of current pipeline development such as misalignment between the pipeline engineer and the team's workflow, the use of infrastructure as code (IaC), and pipeline security Understand the need for CI/CD requirements through the book's non-exhaustive list of more than 60 CI/CD requirements provided to inspire and increase awareness See how certain choices affect the way a pipeline is designed (and realized) Become familiar with branching strategy, build strategy, test strategy, release strategy, and deployment strategy that are explained in detail in the book, including their effect on pipeline design Know how pipelines can be unit tested, using a real-world example Know how performance bottlenecks in a pipeline occur, how they can be detected, and how they can be solved View a complete implementation, including code, showing how the guidelines in this book are applied to a real use case Who This Book Is For DevOps engineers and solution architects involved with automating the software supply chain and using application lifecycle management (ALM)/integration platforms such as Jenkins, CircleCI, Bamboo, and Azure DevOps; intermediate and experienced DevOps engineers (developers, ops engineers, test engineers); and ICT managers interested in the CI/CD pipeline development domain. | ||
| 500 | |a O'Reilly Online Learning Platform: Academic Edition (SAML SSO Access) |5 TMurS | ||
| 650 | 0 | |a Computer software |x Development. | |
| 730 | 0 | |a WORLDSHARE SUB RECORDS | |
| 776 | 0 | 8 | |i Print version: |a van Merode, Henry |t Continuous Integration (CI) and Continuous Delivery (CD) |d Berkeley, CA : Apress L. P.,c2023 |z 9781484292273 |
| 856 | 4 | 0 | |u https://go.oreilly.com/middle-tennessee-state-university/library/view/-/9781484292280/?ar |z CONNECT |3 O'Reilly |t 0 |
| 902 | |a in00006364468 | ||
| 949 | |a ho0 | ||
| 994 | |a 92 |b TXM | ||
| 998 | |a wi |d z | ||
| 999 | f | f | |s 4ccfa201-3919-4881-aae6-7228c5fc3b53 |i 9bfb21ad-401d-48e5-9b0e-6e9785efe997 |t 0 |
| 952 | f | f | |a Middle Tennessee State University |b Main |c James E. Walker Library |d Electronic Resources |t 0 |e QA76.758 |h Library of Congress classification |
