liveBook · Manning

CI/CD server

A CI/CD server is a computer or service that automates software integration, building, testing, packaging, validation, and delivery or deployment tasks.

How 4 Manning books explain it

Automating API Delivery

A build server is a platform that automates tasks in a software delivery pipeline and coordinates its components.

How it is used
Automates delivery-pipeline tasks and checks API design proposals before governance review.
How deep it goes
Explains PR-build triggers, checks, status, and failure investigation, without detailing a complete server configuration.
Examples
Uses an API team's PR title script, Spectral linting, Tufin/oasdiff checks, and GitHub Actions.
What you can do after
Operate/configure it to report PR-check results, fail builds at chosen thresholds, and route remaining issues to reviewers.

Read how Automating API Delivery explains CI/CD server →

Azure Security

A CI/CD platform is a software platform that automates continuous integration and continuous delivery activities such as building, testing, and deploying code.

How it is used
Automates building, testing, and production deployment of repository changes, including security configuration through IaC.
How deep it goes
Walks through service-principal setup, secret configuration, workflow creation, and log verification without detailing workflow syntax.
Examples
Uses GitHub Actions to enable Defender CSPM plans across Azure subscriptions and shows workflow log output.
What you can do after
Operate/configure it to programmatically apply Azure security settings through a GitHub Actions workflow.

Read how Azure Security explains CI/CD server →

Google Anthos in Action

A CI/CD platform is an integrated set of services and tools that automates software integration, testing, delivery, and deployment workflows.

How it is used
Organizes application delivery across infrastructure, developer platforms, applications, and shared operational responsibilities.
How deep it goes
Decomposes platform layers, personas, configuration ownership, and integration points, while avoiding a single prescribed implementation.
Examples
Uses code repositories, image builds, and Kubernetes manifest definitions as shared pipeline interfaces.
What you can do after
Evaluate CI/CD platform designs by comparing layers, responsibilities, configuration ownership, and integration boundaries.

Read how Google Anthos in Action explains CI/CD server →

Learn Docker in a Month of Lunches, Second Edition

A build server is a server or online service that automatically builds software when source changes are pushed.

How it is used
Catches source and build problems early by building pushed changes in a shared environment and alerting the team.
How deep it goes
Explains the role, maintenance burden, and Docker-based replacement, stopping short of detailed server administration.
Examples
Uses a three-stage Dockerfile and the `docker image build -t multi-stage .` command.
What you can do after
Understand how Docker can package a repeatable build environment and separate compilation, testing, and final packaging.

Read how Learn Docker in a Month of Lunches, Second Edition explains CI/CD server →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.