The article explains how a self‑repairing Agent Harness replaces traditional QA by looping evaluation, triage, automated fixing, verification and AI‑gated canary release, using a three‑judge reviewer, model‑based sampling and six daily engineering tasks to keep AI‑driven products reliable.
This guide shows non‑coding test engineers how to understand CI (continuous integration) and CD (continuous deployment), why they’re not exclusive to developers, and three practical actions—business‑scenario requirement submission, targeted testing of generated builds, and rapid feedback—to turn CI/CD into an efficiency partner.
This tutorial explains how Docker can streamline building, testing, and deploying Go web applications, introduces the use of Semaphore for continuous deployment, and walks through creating development and production Dockerfiles, configuring CI/CD pipelines, and managing updates on the server.
vivo’s CICD artifact management has evolved from manual builds to a comprehensive Platform Management 2.0 that provides unified storage, multi‑type support, version control, promotion, security scanning, lifecycle policies, and fine‑grained access, dramatically reducing errors and operational costs.
The article explains that the closer a test is to the code being changed, the easier it is to write effective automated tests, argues for modular, small‑scale units as the ideal test target, and promotes a Python‑focused continuous‑deployment training course.
The article examines continuous deployment, its benefits and challenges, how team incentives and culture shape developers' responses to speed versus quality, and why rapid, incremental releases improve learning, productivity, and morale while avoiding wasteful batch processes.
This article explains continuous integration, continuous delivery, and continuous deployment, outlines their core principles and benefits, presents a typical CI/CD workflow with tools like GitLab, Jenkins, Docker, and Kubernetes, and discusses how DevOps culture ties these practices together for faster, more reliable software releases.
The article argues that merely adopting agile methods does not guarantee faster software delivery; instead, organizations must adopt a value‑driven development mindset, defining and continuously measuring business value to guide product decisions, reduce waste, and accelerate delivery across teams.
The article explains how continuous delivery keeps software always releasable while continuous deployment automates the actual release, discusses the trade‑offs of release frequency, risk, feedback types, and business considerations that guide the decision of when and how to push changes to production.
GitOps, a cloud‑native continuous deployment approach that uses Git as the single source of truth, enables secure, auditable, and multi‑tenant Kubernetes management by automating state reconciliation, supporting multi‑cluster and multi‑environment deployments, and integrating tools like Argo CD, Flux, Helm, and Kustomize.
This article explains the differences between deployment and release, defines continuous deployment, and details various deployment and release strategies such as blue‑green, rolling, dark launch, canary, gray release, and A/B testing, including technical implementations like feature toggles, feature branches, and abstract branches, with real‑world examples from Facebook.
This collection presents five technical articles covering the Spock unit‑testing framework, reasons why automation testing struggles, backend automated testing with continuous deployment, AI‑based UI defect detection, and practical automation of HarmonyOS applications, offering valuable insights for developers and testers.
This article explains the core principles of DevOps, its historical development, the advantages it brings to software delivery, and practical steps for organizations to adopt a collaborative DevOps culture between development and operations teams.
ModelOps and MLOps are transforming AI engineering by introducing continuous training, integration, and deployment, which streamline development cycles, standardize model management, and enable ongoing monitoring to enhance inference accuracy and maximize the business value generated by AI models.
The article explains continuous deployment, using IMVU as a case study to illustrate how rapid release cycles affect software quality, team incentives, and culture, and argues that frequent, small deployments improve learning, reduce waste, and boost morale while challenging traditional batch‑oriented development practices.
This article provides an in‑depth overview of CI/CD within DevOps, covering its core concepts, benefits, implementation steps, tool selections, measurement metrics, real‑world case studies from major enterprises, and future trends such as AIOps and ChatOps.
This article analyses seven years of Facebook mobile development data to show how increasing release frequency can coexist with stable engineer productivity and unchanged software quality, using metrics such as daily code changes, commit frequency, bug severity, crash rates, cherry‑picks and launch‑blockers.
This article examines Facebook's mobile continuous deployment approach, detailing how increased release frequency, automated pipelines, and a clear separation between development and release engineering have allowed weekly Android and iOS updates without sacrificing software quality or developer productivity.
This article explains the full CI/CD pipeline—from code commit, static analysis, building, testing, and artifact storage to continuous deployment, baking, verification, and monitoring—detailing participants, tools, and processes that enable fast, reliable, and automated software delivery in modern DevOps environments.
This article explains the various stages of a CI/CD pipeline, detailing the roles, processes, and tools involved in continuous integration, testing, building, deployment, and monitoring, and highlights why such pipelines are essential for fast, scalable software delivery in modern organizations.
This article surveys common software release strategies—stop‑the‑world, canary, gray/rolling, blue‑green, A/B testing, and traffic‑isolation—detailing their advantages, disadvantages, and ideal scenarios, and then presents Alibaba’s practical best‑practice guide for planning, monitoring, and continuously delivering high‑quality releases.
This article clarifies the distinction between deployment and release, explores historical shifts, and details contemporary strategies such as continuous deployment, on‑demand release, blue‑green, rolling, dark launch, canary, gray releases, A/B testing, and feature toggles, illustrated with real‑world Facebook case studies.
This article explains DevOps as the integration of development and operations, defines Continuous Integration (CI) and Continuous Delivery/Deployment (CD), clarifies their relationship, and briefly touches on Agile development, providing a clear overview of modern software delivery practices.
This comprehensive guide explains the differences between deployment and release, defines continuous deployment and on‑demand release, and details practical strategies such as blue‑green, rolling, dark launch, canary, gray, and A/B testing, supported by feature toggles, feature branches, and real‑world Facebook case studies.
The article explains how Continuous Integration, Continuous Delivery, and Continuous Deployment form a standard software development pipeline, highlighting CI’s role in rapid bug detection, CD’s focus on production‑like testing, and deployment automation that keeps code always ready for release.
This article describes a DevOps‑based continuous deployment practice that integrates project management, code, image, and configuration handling with tools such as Bitbucket, Jenkins, Docker, Harbor, and Kubernetes to achieve automated, one‑click deployments for development and test environments.
The article describes IMVU’s lean‑startup‑inspired continuous deployment system, detailing how they achieve 50 daily releases through automated testing, Buildbot CI, a cluster‑immunity rollback script, rapid user feedback, and extensive QA practices that balance speed with quality.
This article explains how to build, deploy, and continuously update event streaming pipelines using Spring Cloud Data Flow and Apache Kafka, covering common topologies, named destinations, parallel and partitioned streams, function composition, multiple input/output bindings, and practical shell commands for registration and management.
The article explains continuous deployment within the SAFe framework, detailing its definition, role in the four‑stage continuous delivery pipeline, the four sub‑dimensions (deploy, verify, monitor, respond), essential skills for each stage, and why automation, version control, and proactive monitoring are critical for reliable, on‑demand releases.
This article details the design and evolution of Zhihu's deployment platform, covering its early physical‑machine system, the transition to container orchestration with Mesos and Kubernetes, and advanced features such as blue‑green, canary releases, pre‑deployment, and branch deployments that enable rapid, reliable continuous delivery for large‑scale internet services.
This article presents a translated SAFe DevOps health radar, detailing the four dimensions of continuous exploration, integration, deployment, and release on demand, along with 16 sub‑dimensions and rating levels (Sit, Crawl, Walk, Run, Fly) to help teams evaluate and improve their DevOps capabilities.
This article explains the concept of CI/CD, its benefits for agile development, and provides a detailed comparison of seven popular CI/CD tools—including Jenkins, Travis CI, Circle CI, TeamCity, Codeship, GitLab CI, and Bamboo—covering their features, pricing, and ideal use cases.
This article explains how to construct a complete DevOps pipeline using Microsoft Team Foundation Server and Docker to achieve continuous integration and continuous deployment for .NET Core applications, covering pipeline topology, configuration files, build steps, testing, image creation, and release automation.
Continuous Delivery and Continuous Deployment are often confused, but this article examines their origins, definitions, and practical distinctions, highlighting how delivery focuses on business‑level release decisions while deployment automates production releases, and explains how they fit within DevOps, CI, and release strategies.
This article explains the concepts of Continuous Integration, Continuous Delivery, and Continuous Deployment, then walks through a complete VSTS (Azure DevOps) pipeline setup—including project creation, Git configuration, CI build, Release deployment, SSH tasks, Docker image building, and container execution—targeted at automating .NET Core web applications on a cloud server.
Archer, Baidu’s one‑click deployment system, unifies command‑line tools, web services, agents, and plugins to automate code and configuration changes, support multi‑region, hierarchical releases, data transfer, and integration with CI/CD pipelines, dramatically reducing manual errors and improving operational efficiency.
Microservice architecture, built using the Scale Cube Y‑axis approach, splits backend functionality into independent services with dedicated databases, enabling rapid development, continuous deployment, scalability, and fault isolation, while also introducing complexities such as distributed system management, testing challenges, and higher resource consumption.
This article recounts how the Cruise team (later renamed GoCD) tackled the "last mile" problem by implementing continuous deployment through automated pipelines, extensive testing, risk mitigation, and frequent releases, ultimately reducing deployment time and improving software delivery reliability.
This article explains how continuous integration, continuous delivery, continuous deployment, microservices and container technologies interrelate to enable faster, more reliable software delivery, describing CI/CD pipelines, the role of feature toggles, and the benefits of immutable containers in modern DevOps practices.
Continuous Integration, Delivery, and Deployment form a progressive workflow that automates code testing, staging, and production release, enabling teams to detect issues early, ensure deployable code, and achieve fully automated releases despite challenges like complex topologies and large-scale environments.
This article walks through a practical Docker‑based continuous deployment pipeline for a Java application, showing how Git, Jenkins, and Docker Registry can be configured to automatically build, test, and deploy code without manual intervention, complete with screenshots and FAQs.
This article walks through a practical, four‑step workflow that lets developers push Java code to Git, automatically trigger Jenkins to build, create a new Docker image, and redeploy the container without any manual intervention, illustrating the process with screenshots and a FAQ.
