1 views collected around this technical thread.
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.
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.
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 comprehensive guide clarifies the differences between deployment and release, explores continuous deployment concepts, details various deployment and release strategies such as blue‑green, rolling, dark launch, canary, gray, and A/B testing, and examines supporting technologies like feature toggles and branch‑by‑abstraction, illustrated with a Facebook case study.
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 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.
The article explains how to keep CI/CD pipelines reliable by using a single, identical artifact—such as a package, binary, or Docker image—across all environments, recommends externalizing configuration at runtime, and warns against the common trap of mismatched artifacts that cause deployment failures.
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.
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.
This paper describes Facebook's continuous deployment practice for its Android and iOS mobile apps, outlines the release workflow, presents a seven‑year data set covering commits, crashes, and issue tracking, and analyses how deployment frequency, team size, and release timing affect developer productivity and software quality.
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.