0 views collected around this technical thread.
The article explains the core concept of deployment pipelines in Continuous Delivery 2.0, outlines essential quality‑gate mechanisms, and details five design principles—build once, loose coupling, parallelization, fast feedback, and important feedback—plus team collaboration disciplines such as immediate pause and security audit.
This article explains what a deployment pipeline is, outlines design principles for keeping pipelines simple and efficient, describes how pipeline design relates to branch strategies, and provides detailed naming conventions and label rules for different pipeline types, triggers, and quality‑gate metrics.
This article explains software delivery pipelines, covering their components, deployment stages, continuous integration and delivery practices, and release strategies such as blue/green and canary deployments, highlighting how automation improves reliability and reduces risk.
The article examines how the automotive industry adopts continuous delivery and DevOps techniques—detailing deployment pipelines, distributed embedded ECUs, safety‑critical testing, tooling, and real‑world observations from Tesla’s firmware release cycles—to illustrate the unique challenges and emerging solutions for rapid, reliable software updates in vehicles.
This article provides a comprehensive guide to continuous delivery, covering its definition, consensus and management mechanisms, required infrastructure, configuration and testing strategies, trunk and local development practices, six‑step commit workflow, code review, metrics, DevOps concepts, and information traceability.
This article explains the components, tools, and stages of software delivery pipelines—including version control, continuous integration, continuous delivery, blue/green and canary deployments—while highlighting their automation benefits and offering resources for further learning.
This article explains the distinction and relationship between continuous delivery, continuous deployment, and continuous release, emphasizing the need to decouple technical actions from business decisions, focusing on rapid, safe, and sustainable value delivery through well‑designed deployment pipelines and release strategies.
This article chronicles the progression of continuous integration practices—from an initial linear build script to stage‑based, process‑oriented, and finally pipeline‑style CI—illustrating how teams can iteratively refine automation, balance feedback speed, and scale resources to achieve reliable, fast software delivery.
The article traces the impact of Ford’s 1910 assembly line on software delivery, explains Jez Humble’s definition of deployment pipelines, showcases continuous delivery concepts, and presents real-world examples from Baidu, Netflix, and an open-source end-to-end pipeline, highlighting key design points for DevOps transformation.
Meiya addresses typical startup challenges—small user base, rapid requirement changes, and an evolving team—by prioritizing development efficiency through standardized RESTful communication protocols, a four‑stage deployment pipeline, reusable frameworks, DB migrations, command‑line tools, logging with ELK, and automated server management via SaltStack.