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.
Discover how modern PHP development has evolved with powerful tools like Composer, PHPUnit, Behat, and IDE integrations, while embracing best practices, PSR standards, micro‑frameworks, and continuous integration to boost productivity, code quality, and maintainability in today’s fast‑moving ecosystem.
This article examines the shortcomings of traditional software development, explains the concepts of continuous integration and CI servers, outlines the benefits of adopting CI, and provides practical best‑practice recommendations while also addressing common challenges teams may face.
The article chronicles Youzan's transition from a monolithic PHP system to Java‑based microservices, outlines the architectural challenges encountered, and presents practical solutions such as Spring Boot adoption, BOM management, health‑check standardization, Hystrix circuit‑breaker patterns, automated API documentation, contract testing, and continuous integration to improve scalability, maintainability, and operational efficiency.
This article explains the true practice of Continuous Integration, introduces Martin Fowler’s definition, details a six‑step commit workflow (the “check‑in‑dance”), addresses common team questions, and offers practical tips such as token control and visual CI status monitoring.
Learn step‑by‑step how to install Jenkins on Windows, configure the service port, create a Maven job with Subversion source control, set up build triggers, post‑build actions, and email notifications, then run and monitor builds through the Jenkins web UI.
This guide explains how to configure Jenkins to run Android Monkey tests on both emulators and real devices, covering plugin installation, build environment setup, parameterized builds, command-line options, and post-build result publishing for continuous integration of mobile stability testing.
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.
The article examines common challenges in legacy continuous‑integration pipelines—long build times, unstable tests, and complex dependencies—and presents a systematic, Theory‑of‑Constraints‑based approach that includes parallelization, mocking, infrastructure upgrades, test isolation, contract testing, and monitoring to improve build speed, reliability, and overall delivery efficiency.
The article introduces Cable, Qunar's internal continuous integration platform that combines automated static code checks, environment validation, rapid feedback, and flexible configuration to improve development efficiency, reduce release failures, and enhance overall product quality within a fast‑paced online travel business.
This article provides a comprehensive guide to Android app compilation, detailing the step‑by‑step build process, the use of Ant and Gradle tools, configuration of build.xml and build.gradle files, and essential settings such as obfuscation, signing, multidex, and code coverage to streamline CI pipelines.
This guide explains how to configure a cross‑platform CI pipeline for iOS apps using VSTS/TFS, covering project setup, Git repository linking, agent installation on macOS, build definition creation, variable configuration, and triggering builds to produce signed IPA packages.
This article explains the importance of unit testing in Android development, outlines why developers should invest time in it, and provides a step‑by‑step guide on writing effective Android unit tests using JUnit, Mockito, Dagger2, and Robolectric, along with practical tips, CI integration, and common pitfalls.
SonarQube, an open‑source code quality platform, offers extensive static analysis for Android (Java) projects through plugins that assess complexity, duplication, test coverage, coding standards, comments, potential bugs, and architectural design, and integrates with IDEs and CI tools such as Jenkins to visualize and reduce technical debt.
This article outlines how a product line can achieve highly stable, rapid, and universally applicable testing services within a continuous integration pipeline by employing gray‑release, hierarchical builds, automated test case selection, subsystem decoupling, generic stubs, and a unified testing platform.
This guide explains how to set up bi‑directional synchronization between public GitHub repositories and private VSTS (Azure DevOps) repos using VSTS CI pipelines, covering configuration steps, command‑line tasks, token handling, and common synchronization scenarios.
This article shares practical experiences and best practices for Android unit testing, covering why testing matters, simple test structures, mocking with Mockito, dependency injection via Dagger2, using Robolectric, CI integration, common pitfalls, and a detailed checkout flow example.
The article introduces php-code-coverage, an open‑source library that collects, processes, and visualizes PHP code‑coverage data, explains its measurement metrics such as line, function, and class coverage, and shows how to integrate it with PHPUnit, Composer, and Jenkins for automated testing and quality assessment.
This guide explains how to install Node.js, download the TFS Build vNext agent, configure it on Windows using PowerShell, set execution policies, and register the agent with TFS, covering required tools, configuration options, and optional service setup.
This article explains Baidu's continuous integration (CI) journey, detailing the CI capability model, its three core factors—test coverage, build system, and team habits—along with metrics, scoring, and how the CI team supports product lines to improve development efficiency.
