Skip to main content
Top

2023 | OriginalPaper | Chapter

4. Pipeline Design

Author : Henry van Merode

Published in: Continuous Integration (CI) and Continuous Delivery (CD)

Publisher: Apress

Activate our intelligent search to find suitable subject content or patents.

search-config
loading …

Abstract

This chapter covers the following:

Dont have a licence yet? Then find out more about our products and how to get one now:

Springer Professional "Wirtschaft+Technik"

Online-Abonnement

Mit Springer Professional "Wirtschaft+Technik" erhalten Sie Zugriff auf:

  • über 102.000 Bücher
  • über 537 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Maschinenbau + Werkstoffe
  • Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

Springer Professional "Technik"

Online-Abonnement

Mit Springer Professional "Technik" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 390 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Maschinenbau + Werkstoffe




 

Jetzt Wissensvorsprung sichern!

Springer Professional "Wirtschaft"

Online-Abonnement

Mit Springer Professional "Wirtschaft" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 340 Zeitschriften

aus folgenden Fachgebieten:

  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Versicherung + Risiko




Jetzt Wissensvorsprung sichern!

Footnotes
1
Some stages are implemented differently, which means that tasks move to a different stage, and the stage ends up with zero tasks, in other words, the [0..n] range. In other contexts, some stages are not applicable, meaning that the stage has zero tasks and is therefore not implemented.
 
2
Or it is triggered manually, of course.
 
3
On an infrastructure level, this also means that the external system calling the API of the ALM platform must be an authenticated system. So, connections should make use of mTLS, OpenID Connect, or at least some basic authentication.
 
4
Signing a package means that a digital signature is created and added to an artifact, to guarantee the integrity of the artifact.
 
5
Continuous delivery is sometimes used as overarching concept that includes continuous integration.
 
6
This applies only to regular deployments and is not a rollback to a previous version because of an incident.
 
7
In theory, of course. Often there are still manual test tasks to be performed.
 
8
From a technical (Git) point of view, you can decide to merge the feature branch back to main, or rebase main onto the feature branch, to get a cleaner history. In addition—if the platform supports it—you may define branch policies on the main branch to prevent, for example, that a feature is merged that does not even build successfully.
 
9
The release version in production must always be lower than the deployed release version.
 
10
Not all database changes are backward compatible. Sometimes, some additional processing or transformation is required in the database using database triggers, for example.
 
11
Microservices are loosely coupled but not decoupled. If a new mandatory element is added to an event between two microservices, both microservices are impacted.
 
12
This is also a downside of an event-based model; if the workflow is not explicit anymore, one can lose track of the workflow as a whole.
 
13
SonarQube requires an artifact, but this can still be a task detached from the creation of a regular build artifact.
 
Metadata
Title
Pipeline Design
Author
Henry van Merode
Copyright Year
2023
Publisher
Apress
DOI
https://doi.org/10.1007/978-1-4842-9228-0_4

Premium Partner