東華大學圖書館 |

Language: English

Help

回圖書館首頁

手機版館藏查詢

Back

Switch To: Labeled | MARC Mode | ISBD

Continuous Integration (CI) and Cont...

Merode, Henry van.

Linked to FindBook

Google Book

Amazon

博客來

Continuous Integration (CI) and Continuous Delivery (CD) = a practical guide to designing and developing pipelines /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Continuous Integration (CI) and Continuous Delivery (CD)/ by Henry van Merode.
Reminder of title:	a practical guide to designing and developing pipelines /
Author:	Merode, Henry van.
Published:	Berkeley, CA :Apress : : 2023.,
Description:	xiii, 422 p. :ill., digital ;24 cm.
[NT 15003449]:	Chapter 1. The CI/CD Pitfall -- Chapter 2. Concepts -- Chapter 3. Requirements Analysis -- Chapter 4. Pipeline design -- Chapter 5. Pipeline Development -- Chapter 6. Test Pipelines -- Chapter 7. Pipeline Implementation -- Chapter 8. Operate and Monitor -- Chapter 9: Use Case.
Contained By:	Springer Nature eBook
Subject:	Computer software - Development. -
Online resource:	https://doi.org/10.1007/978-1-4842-9228-0
ISBN:	9781484292280

Continuous Integration (CI) and Continuous Delivery (CD) = a practical guide to designing and developing pipelines /
Merode, Henry van.

Continuous Integration (CI) and Continuous Delivery (CD)a practical guide to designing and developing pipelines /[electronic resource] :by Henry van Merode. - Berkeley, CA :Apress :2023. - xiii, 422 p. :ill., digital ;24 cm.

Chapter 1. The CI/CD Pitfall -- Chapter 2. Concepts -- Chapter 3. Requirements Analysis -- Chapter 4. Pipeline design -- Chapter 5. Pipeline Development -- Chapter 6. Test Pipelines -- Chapter 7. Pipeline Implementation -- Chapter 8. Operate and Monitor -- Chapter 9: Use Case.

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.

ISBN: 9781484292280

Standard No.: 10.1007/978-1-4842-9228-0doiSubjects--Topical Terms:

542671
Computer software
--Development.

LC Class. No.: QA76.758

Dewey Class. No.: 005.1

Continuous Integration (CI) and Continuous Delivery (CD) = a practical guide to designing and developing pipelines /
LDR:03246nmm a2200325 a 4500 001 2318151
003 DE-He213
005 20230329130821.0
006 m d
007 cr nn 008maaau
008 230902s2023 cau s 0 eng d
020 $a 9781484292280 $q (electronic bk.)
020 $a 9781484292273 $q (paper)
024 7 $a 10.1007/978-1-4842-9228-0 $2 doi
035 $a 978-1-4842-9228-0
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.758
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
072 7 $a UMZ $2 thema
082 0 4 $a 005.1 $2 23
090 $a QA76.758 $b .M567 2023
100 1 $a Merode, Henry van. $3 3632904
245 1 0 $a Continuous Integration (CI) and Continuous Delivery (CD) $h [electronic resource] : $b a practical guide to designing and developing pipelines / $c by Henry van Merode.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2023.
300 $a xiii, 422 p. : $b ill., digital ; $c 24 cm.
505 0 $a Chapter 1. The CI/CD Pitfall -- Chapter 2. Concepts -- Chapter 3. Requirements Analysis -- Chapter 4. Pipeline design -- Chapter 5. Pipeline Development -- Chapter 6. Test Pipelines -- Chapter 7. Pipeline Implementation -- Chapter 8. Operate and Monitor -- Chapter 9: Use Case.
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.
650 0 $a Computer software $x Development. $3 542671
650 1 4 $a Software Engineering. $3 890874
650 2 4 $a Web Development. $3 3134872
650 2 4 $a Computer Engineering and Networks. $3 3538504
650 2 4 $a Hardware Performance and Reliability. $3 3538539
710 2 $a SpringerLink (Online service) $3 836513
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-1-4842-9228-0
950 $a Professional and Applied Computing (SpringerNature-12059)