This article provides a comprehensive overview of continuous integration and delivery, covering traditional release challenges, CI/CD concepts, Jenkins architecture, personal implementation experiences, and practical advice for mastering DevOps pipelines and automation.
The article uses a whimsical conversation between a developer and a testing deity to explore why testing is essential, how it functions as sampling, the limits of defect detection, and practical strategies such as TDD, continuous integration, and requirement control to improve software quality.
This guide demonstrates how to use a single Dockerfile and Jenkins to test a Node.js project against multiple Node versions in a CI pipeline, leveraging Docker build arguments, custom scripts, and volume caching to simplify environment management without installing numerous tools.
Built‑in quality emphasizes integrating quality throughout the software development lifecycle, using agile principles, continuous integration, test‑driven development, code review, and shared code ownership to reduce technical debt, avoid rework, and ensure reliable, maintainable products.
This article examines the DevOps standard, highlights common pitfalls through two case studies, and offers practical implementation paths and guiding principles to help organizations successfully adopt DevOps across development, testing, and operations teams.
After a year of DevOps pilot work, the Agricultural Bank of China's personal online banking system built a fully automated, end‑to‑end delivery pipeline covering configuration, build, test, deployment and monitoring, enabling rapid, reliable releases for a user base of over a hundred million.
This guide explains the fundamentals of Continuous Integration (CI), compares popular CI tools like Jenkins and GitLab CI, and provides detailed, cross‑platform instructions for installing Docker, setting up GitLab‑CI runners, configuring permissions, and registering runners with various token types for seamless automated builds.
This article explains the concept, black‑box and white‑box approaches, and the end‑to‑end technical solution of traffic replay testing for microservice back‑ends, detailing recording and playback processes, a Kubernetes‑based distributed execution platform, result calibration, and future enhancements.
This article chronicles the four evolutionary stages—Stone Age, Silver Age, Golden Age, and Future Age—of Alibaba's Taobao front‑end development and deployment, detailing tool migrations, automation breakthroughs, cloud‑build integration, quality‑gate systems, and the emerging IDE platform that unifies the entire workflow.
This article describes how the Beetle platform, together with the LuBan system, automates multi‑branch creation, testing, gray release, and hot‑fix processes for app development, addressing challenges of branch‑demand association, merge coordination, and version synchronization to improve delivery speed and quality.
This article details the evolution of Zhihu's deployment platform, covering its early physical‑machine system, the transition to container orchestration with Kubernetes, and the implementation of blue‑green, canary, and pre‑release strategies that enable fast, reliable continuous deployment.
The Tongtian Tower visual CMS team optimized its build, dependency packaging, and pre‑release workflows in Q1 2020 by migrating to webpack 4, parallelizing template builds, and improving FTP uploads, cutting total release time from 358 seconds to 160 seconds and saving roughly 7 hours of developer effort per week.
This article explains the drawbacks of the traditional software release process, introduces continuous integration, delivery, and deployment concepts, compares GitLab CI/CD with Jenkins, and outlines the architecture, configuration files, and advantages of using GitLab’s built‑in CI/CD platform.
This article explains the shortcomings of the traditional software release process, introduces continuous integration, delivery, and deployment concepts, compares GitLab CI and Jenkins features, and outlines the advantages, architecture, and practical usage of CI/CD pipelines for DevOps teams.
This guide explains GitLab CI/CD fundamentals, including continuous integration, delivery, deployment, .gitlab-ci.yml configuration, runner setup, pipeline stages, Auto DevOps, and Kubernetes deployment, with practical code examples and visual walkthroughs for automating software delivery.
This article provides a comprehensive overview of DevOps concepts, including definitions of CI, CD, continuous deployment, version control, tooling, implementation steps, benefits, and distinctions from Agile and Lean IT, offering guidance for effective adoption and interview preparation.
This guide outlines a six‑step framework for creating an effective test automation strategy, covering scope definition, methodology, risk analysis, environment setup, execution planning, and continuous review to prevent costly production bugs.
This article explains how Slack’s engineering team designs a multi‑stage deployment pipeline—including release branches, staging, dogfood, canary, and percentage rollouts—while emphasizing rapid iteration, visibility, and reliability through fast and atomic deployment mechanisms.
QAOps integrates continuous testing from DevOps into the software development lifecycle, combining automated testing, parallel execution, and scalable reporting to improve collaboration between QA engineers, developers, and operations teams while accelerating and stabilizing software releases.
This article presents a comprehensive overview of the 14 most popular CI/CD tools, describing their main functionalities, licensing models, and official websites to help teams choose the most suitable solution for fast and reliable software delivery.
The article explains how agile testing reshapes software development by promoting simultaneous dev‑test activities, cross‑functional collaboration, continuous integration tools, clear communication, and rapid feedback loops that together accelerate delivery and improve product quality.
This article explains the core concepts of continuous integration, delivery, deployment, and testing, outlines common challenges such as limited environments and ownership issues, and highlights why CI/CD is vital for improving developer productivity, code quality, and faster software releases.
This article explains the fundamentals of unit testing, covering its definition, core concepts, essential principles, practical techniques such as mocking, and its role in test automation and continuous integration within modern agile development.
During the COVID‑19 pandemic, SequoiaDB detailed how its distributed network, virtual desktop setup, management services, and multi‑level automated testing pipeline enable remote developers and testers to maintain high‑quality database releases across dozens of locations.
Facing a 24‑million‑line codebase with over 100 third‑party pods, the team tackled slow Xcode compilation, lengthy packaging, and merge‑request bottlenecks by applying build‑setting tweaks, RAM‑disk compilation, CCache, and a custom binary‑pod workflow that automates packaging, publishing, and integration without altering source projects.
The article outlines why moving from isolated architectures to a collaborative DevOps system requires cultural change, phased implementation steps, strong leadership, appropriate tooling, and continuous monitoring to achieve sustainable automation and delivery.
This article provides an overview of three continuous integration solutions—CircleCI, Travis CI, and Jenkins—detailing their key features, supported platforms, licensing models, and a comparative table to help teams choose the most suitable CI tool based on their needs.
Youzan’s Efficiency Improvement team applied lean manufacturing principles and DevOps practices—quantifying technical debt, automating high‑coverage unit tests, streamlining continuous integration, and fostering a culture with visual CI indicators—to eliminate waste, accelerate integration cycles, and markedly boost overall software development efficiency.
Implementing an effective CI/CD pipeline involves understanding continuous integration, delivery, and deployment, recognizing their benefits such as faster feedback and early error detection, and following key stages—from commit and build to testing and production deployment—while selecting appropriate tools and practices to streamline software delivery.
This article explains the importance of continuous integration for maintaining code quality in enterprise development, defines CI and its core principles, and reviews several popular free open‑source CI tools—including Travis CI, Jenkins, Circle CI, and Drone CI—providing brief usage insights and project links.
This article explains the G7 IoT platform's comprehensive automated testing framework, covering use‑case design, full‑link coverage, data validation strategies, keyword encapsulation, and thread‑group isolation to achieve high‑quality, rapid releases for complex IoT systems.
This article presents a comprehensive, practice‑oriented overview of Domain‑Driven Design, covering its conceptual foundations, project‑level management, architectural layering, design patterns, implementation techniques with Java/Spring, testing, continuous integration, and deployment strategies for enterprise applications.
The article explains how large organizations, especially U.S. government agencies, can adopt DevOps as a service by addressing cultural resistance, talent shortages, functional silos, authority‑to‑operate hurdles, and securing the toolchain and software supply chain through automation, training, and integrated security practices.
The article examines the frequent reasons test automation projects collapse—from unrealistic 100% automation expectations and poor management visibility to inadequate manual testing, tool mis‑selection, false positives, and lack of collaboration—offering practical guidance to improve automation success.
To overcome fragmented C++ builds across mobile, car‑machine and open‑platform teams, Gaode Map created the Python‑driven Abtor tool that generates CMake projects and manages cloud‑hosted dependencies, and paired it with the scalable Amap CI pipeline, enabling unified, cross‑platform compilation, automated testing, and permission‑controlled library publishing.
The article shares Winter's presentation on building a high‑quality, efficient frontend team, covering demand models, toolchains, continuous integration, reusable architecture, business value, data‑driven thinking, and the Weex innovation case, while also providing recruitment information for the ZooTeam.
This article shares JD's front‑end team's experience engineering large‑scale mini programs, covering standards, single‑page extraction, code duplication removal, automated testing with a sandbox, package‑size optimization, smart splitting, conditional compilation, and a continuous‑integration pipeline that together address the challenges of rapid growth and release complexity.
This article provides a curated collection of Jenkins continuous integration tutorials, covering introductory topics such as Jenkins overview and installation, integration guides for tools like GitLab, Nexus, LDAP, and advanced practice articles on pipelines, containerized slaves, and monitoring, serving as a comprehensive resource for DevOps practitioners.
This article summarizes Google’s core software‑engineering practices—including a unified source repository, the Blaze build system, rigorous code‑review processes, extensive testing, error tracking, language policies, debugging tools, release engineering, project‑management methods, and personnel development—showing how they contribute to the company’s sustained technical success.
The Ctrip Technology Salon gathered over 250 experts and practitioners from Ctrip, Huawei, NetEase and others to discuss how AI, automated testing platforms, DevOps, and natural‑language testing frameworks can dramatically improve test engineering efficiency and software quality.
The article examines Alipay's mobile DevOps implementation, contrasting it with web DevOps, outlining development stages, highlighting technical and operational challenges such as fragmented device ecosystems, quality assurance, continuous integration, and the impact of emerging technologies on the mobile development workflow.
The article explains how shifting from fragile GUI‑level testing to automated API testing improves reliability, speed, and coverage in agile development, offering concrete strategies, examples, and tool recommendations for integrating API contracts into continuous integration pipelines.
Interviews with 14 IT experts reveal that slow adoption, skill shortages, costly manual processes, and insufficient organizational support hinder automated testing, while opportunities exist through better tooling, containerization, and focused training to improve ROI and software quality.
This article provides an overview of Jenkins, covering its origins, key features, development history, web UI components, project types, parameter options, and trigger mechanisms, illustrating why it is a widely used open‑source automation tool in modern software delivery pipelines.
Testin Pro is a cloud‑based mobile automation testing platform that details its network topology, server configuration, user roles, key functionalities such as online script recording and automated execution, and its integration with the bank's ATP DevOps pipeline to improve testing efficiency and resource utilization.
This document provides a detailed, chapter‑by‑chapter guide to Jenkins, covering its fundamentals, installation on various platforms, management, integration with tools, pipeline creation for frontend, backend, and mobile projects, as well as container deployment and monitoring solutions.
This article outlines comprehensive best‑practice guidelines for building microservice systems, covering source‑code management, development environments, continuous integration and delivery, deployment packaging, automated rollout, feature‑flag usage, configuration handling, centralized logging and monitoring, autoscaling, external service integration, and team ownership throughout the service lifecycle.
This article explains the need for DevOps, contrasts it with ITIL, outlines practical steps for implementation, and shares Vipshop’s component‑centric DevOps practice, including configuration platforms, risk‑matrix control, and continuous improvement metrics, offering engineers actionable insights for real‑world deployment.
This article presents a detailed overview of the 58 Deployment System (USP), covering its evolution, Java‑based architecture, communication and deployment models, traffic management, one‑stop and parallel deployments, gray‑scale rollout, fast rollback, task‑driven workflow, and future direction within private‑cloud environments.
This article details a practical approach to implementing automated testing in an information systems team, covering technology selection, framework setup, and real-world challenges encountered during the process.
This article examines Microsoft’s DevOps transformation, detailing the shift to a trunk‑based Release Flow, the new branch strategy, pull‑request workflow, hot‑fix process, and how these practices dramatically boost engineering speed, reliability, and large‑scale deployment across data centers.
This article explains how a frontend team migrated from SVN to GitLab, leveraged GitLab CI/CD to automate building and publishing HTML assets, outlines the previous manual workflow, details the new CI/CD pipeline, runner configuration, .gitlab-ci.yml structure, encountered issues, and future improvements.
The 2019 Enterprise‑Level DevOps Empowerment Forum in Chengdu gathered experts from major Chinese banks and telecoms to share practical experiences, including China Merchants Bank’s K8s‑based pipeline, measurement challenges, and collaborative Q&A, illustrating how organizations can accelerate DevOps adoption and improve delivery efficiency.
This article explains how Xianyu transformed its fast‑growing business by adopting a lean 2‑1‑1 development model and building an automated, unmanned client‑side continuous integration pipeline that cuts release cycles, reduces manual effort, and improves quality through measurable metrics.
This article explains how CI/CD transforms software release practices by detailing continuous integration, delivery, and deployment, describing their benefits, challenges, and common tools such as Jenkins, while highlighting the role of pipelines and cloud environments in modern DevOps workflows.
This article details Youzan's comprehensive frontend quality assurance system, covering architecture overview, UI automation with Puppeteer and Mocha, Node interface testing using Istanbul, unit testing choices, library change alerts, Sentry error monitoring, business alarms, and standardized release processes to ensure reliable releases.
This article provides a comprehensive overview of Jenkins, covering its definition, key features, historical evolution from Hudson, and detailed descriptions of its web UI components such as management, project, and build pages, as well as project types, parameters, and triggers.
This document provides a comprehensive outline of Jenkins practice, covering fundamentals, installation on various platforms, management, integrations with tools like Maven, GitLab, and SaltStack, and detailed pipeline examples for front‑end, back‑end, and mobile projects.
This article shares practical DevOps insights—covering waste elimination, automation, disaster coverage, comprehensive documentation, and change control—to help developers and operators build resilient, collaborative, and efficient production pipelines.
This article compares Alibaba’s change request workflow with traditional Pull/Merge Request models, outlining their similarities, key differences, benefits such as flexibility and faster releases, as well as associated risks, and explains how the method is implemented and supported by tools like Cloud Eff.
This article recounts how an agile coach helped Alibaba Health's B2B development team overcome chronic release failures, burnout, and low productivity by establishing stable feature teams, aligning goals, tightening quality gates, clarifying requirements, visualizing flow with Kanban, implementing continuous integration, and driving continuous improvement through clear metrics.
Zhihu built a Docker‑based Jenkins Pipeline system that now runs over 3,000 jobs daily, offering low entry cost, high customizability, language openness, fast stable builds, and a highly available, extensible cluster while reducing debugging effort and enforcing quality standards.
This guide walks through creating an Azure DevOps project, configuring a new build pipeline linked to a GitHub repository, customizing build steps for a .NET Standard library, enabling continuous integration and pull‑request validation, adding a status badge to the README, and running the pipeline to verify successful builds.
By adopting a lean 2‑1‑1 development cycle and a fully automated CI pipeline that binds demand branches to packaging, triggers builds, runs scheduled and merge‑request tests, and provides instant feedback, Xianyu’s mobile client team cut release cycles from a month to two weeks, increased integration frequency, improved quality, and moved toward a 24/7 unmanned release process.
This article presents a comprehensive case study of how a major Chinese bank transformed its legacy C‑based IT system development by designing and deploying a fully automated, end‑to‑end CI/CD pipeline with Azure DevOps Server (formerly TFS), covering static code analysis, mandatory code review, continuous integration, automated testing, and release management to accelerate delivery and improve quality.
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.
Jiangsu Mobile’s DevOps‑driven integrated monitoring platform unifies development, testing, and production operations through self‑developed automated web and API testing tools, Selenium‑based keyword‑driven frameworks, and JMeter‑powered performance monitoring, enabling full‑life‑cycle visibility, asset reuse, and 24/7 critical service oversight.
The article outlines six practical criteria—trunk‑based development with frequent commits, task‑complete commits, sub‑10‑minute build verification, blocking new commits after failures, rapid fix or rollback within ten minutes, and confidence from successful automated builds—to help teams evaluate whether their continuous integration practice has reached an optimal state.
This article examines common misconceptions and mistakes in implementing Agile and DevOps—such as misusing Scrum, overly long daily stand‑ups, indiscriminate automation testing, superficial CI pipelines, and ineffective Kanban—while offering concrete, principle‑driven practices to achieve efficient, high‑quality software delivery.
This article shares Meitu's DevOps journey, detailing how the company restructured its organization, adopted agile practices, cultivated an engineer culture, implemented continuous integration, and built a unified monitoring system to create a high‑efficiency operations team.
At Tubi, the Hubble release‑management platform was created to tackle the complexities of synchronizing and deploying code across more than a hundred devices, automating changelog generation, Slack notifications, test‑environment tracking, and CI performance reporting, thereby reducing manual overhead and accelerating multi‑platform iteration.
This article presents a comprehensive catalog of mobile testing tools and techniques, covering Android and iOS platforms, including UI automation frameworks, unit testing libraries, performance monitoring utilities, network simulation tools, static analysis solutions, code coverage options, cloud testing services, and continuous integration pipelines.
This article summarizes essential DevSecOps concepts from the DevOps Handbook, explaining how to embed security throughout the software lifecycle—from making security a shared responsibility to integrating automated checks in development, testing, deployment pipelines, and change management—while highlighting real‑world examples and practical recommendations.
This article surveys twenty essential DevOps tools—from project planning and version control to continuous integration, monitoring, and cloud services—explaining their core functions, typical use cases, and how they fit into a modern software development lifecycle.
Feature flags (toggles) and feature branches are two strategies for managing new functionality in software development; this article compares their pros and cons, explains when to use each, presents best practices, implementation examples in PHP/Smarty, and lists open‑source frameworks across multiple languages.
This article provides a comprehensive overview of the daily work of the Shanghai R&D Center Test Team at Dada-Jingdong to Home, covering project quality assurance, automation, tool construction, and quality culture building.
The article discusses challenges of regression testing and proposes an incremental code‑coverage solution using a diff engine, AST analysis, and JaCoCo integration within a Jenkins CI pipeline, enabling precise test scope identification, visual coverage feedback, and improved collaboration between manual and automated testing.
This article explains how the PouchContainer project automates code‑style enforcement and comprehensive Golang unit testing using tools like golint, gometalinter, shellcheck, markdownlint, table‑driven tests, and mock implementations, integrating them into CI pipelines to ensure reliable releases.
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.
This article explains the concept and advantages of continuous integration, outlines a typical CI workflow including submission, testing, building, deployment and rollback, discusses challenges in test case management, reviews popular CI tools such as Jenkins and Qone, and details code‑coverage measurement using Jacoco with Maven configuration.
The article discusses how embracing speed and flexible configuration in QA, exemplified by the Beetle platform’s interface testing workflow, can improve project efficiency, enable unified automated testing, and integrate continuous integration, while emphasizing that tools alone cannot guarantee test quality.
The article details JD Logistics’ quality department’s evolution of its automated testing platform, Linglong, describing the business background, limitations of the previous system, the new architecture, core functionalities such as task scheduling, multi‑task execution, data‑driven testing, and future development plans.
Meituan Dianping’s Mobile Continuous Integration (MCI) architecture tackles tangled component dependencies, fragmented workflows, and long build times by combining GitLab‑based CI pipelines, dependency flattening, binary integration with multi‑threaded caching, a custom static‑analysis framework, comprehensive logging, monitoring, and a centralized configuration portal, achieving roughly 60 % faster iOS builds and 50 % faster Android builds.
Meizu’s operations team transformed reactive firefighting into proactive delivery by building a cloud‑native continuous integration platform, detailing their automation journey, challenges, platform components, release evolution, and intelligent ops that together boost quality, efficiency, cost control, and security.
Meituan Waimai iOS achieved an 84 % code‑reuse rate across its standalone app, Meituan channel, and Dianping channel by progressively componentizing business logic into layered CocoaPods, flattening dependencies, using binary pods for fast builds, and employing a robust toolchain and coordination among PM, RD, and QA.
This article explores the concept of engineer culture versus KPI‑driven culture, outlines essential prerequisites such as trust and technical leadership, and shares concrete practices—including small‑team dynamics, automated testing, continuous integration, pair programming, and effective meetings—to help teams cultivate a sustainable, high‑impact engineering environment.
This article examines how DevOps emerged from the merging of development and operations roles, explores automation practices in small and large teams, outlines the three-step DevOps workflow, and discusses the cultural and organizational challenges of adopting DevOps at scale.
This article outlines the motivation, tool comparison, and detailed step‑by‑step process for implementing static code scanning across Android and iOS codebases, emphasizing the selection of Infer and the integration of scanning results into CI pipelines and issue‑tracking workflows.
This article presents a detailed mobile testing automation solution covering quality assurance, early test involvement, systematic automation processes, benefit measurement, and team development to improve product quality and testing efficiency across the entire software lifecycle.
This guide explains the core concepts of Continuous Integration, Continuous Delivery, and DevOps, showing why they matter for product teams, how they improve software release speed and reliability, and what steps organizations can take to adopt these practices effectively.
This article explains Alibaba’s AoneFlow branch management method, comparing it with TrunkBased, GitFlow, and GithubFlow, detailing its three core rules, automation tools, and how it balances continuous integration with feature-driven development for efficient, scalable software delivery.
This article describes how Qunar built a comprehensive automated testing system triggered by beta releases, incorporating CI‑driven execution, strong release‑blocking controls, and multi‑channel result notifications to improve release quality, reduce manual effort, and close testing gaps in a fast‑moving internet environment.
This article explains how agile development—especially Scrum—and agile testing practices like continuous testing, TDD, automation, and continuous integration enable rapid iteration, higher product quality, and faster delivery in fast‑changing market environments.
The article explains DevOps culture, the shift toward eliminating barriers between development and operations, and outlines key practices such as frequent small releases, microservices, continuous integration, continuous delivery, and infrastructure as code to accelerate innovation while maintaining reliability.
Continuous Integration (CI) is a DevOps practice where developers frequently merge code into a shared repository, triggering automated builds and tests to quickly detect defects, improve software quality, and accelerate delivery, while fostering a culture of frequent integration and reducing manual release effort.
This article explains why modern software projects must shorten client acceptance cycles and outlines six practical methods—defining acceptance criteria, managing test data, providing alpha versions, setting tester boundaries, clarifying stage scopes, and ensuring transparent test case management—to achieve rapid, high‑quality releases.
This article explains the DevOps concept, its historical evolution, the advantages of faster and more reliable software delivery, the cultural and technical drivers behind its rise, and current adoption trends and tools used by enterprises worldwide.
The article introduces ArthurCI, a front‑end continuous‑integration platform developed by 58, detailing its design, performance optimizations such as yarn caching and parallel webpack compression, ease‑of‑use integration steps, stability features, and future data‑driven enhancements, while comparing it with tools like TravisCI.
This article details how the AutoV IT framework addressed low test coverage, high maintenance costs, and data dependencies in a shopping‑cart checkout system, introducing embedded service startup, mock services, Excel‑driven test cases, and parallel execution to achieve up to 30% faster testing cycles and significantly higher confidence in releases.
