This guide explains how to efficiently deploy a React frontend to a private server by either uploading the compiled build folder or pushing source code to a bare Git repository, then using a post‑receive hook to automatically build, package, and serve the application with Nginx.
This article provides a detailed, step‑by‑step guide for startups to design and select a complete backend technology stack, covering language choices, components, processes, systemization, and the practical evaluation of tools such as project management, DNS, load balancing, databases, messaging, CI/CD, monitoring, and deployment.
This guide explains how to use GitHub Packages as a unified package registry and demonstrates step‑by‑step how to configure npm, create a workflow file, and automatically publish a Node.js package to GitHub Packages via GitHub Actions whenever a new release is created.
This article presents a collection of visual diagrams illustrating Kubernetes cluster structures, OpenShift/Kubernetes architectures, and several common CI/CD pipeline designs, providing readers with clear reference material for modern cloud‑native operations and deployment workflows.
This guide explains how to efficiently deploy a React project to a private server by describing two CI/CD approaches—deploying compiled files or the source code—setting up a bare Git repository with a post‑receive hook, configuring Nginx for static serving, and pushing code from the client to trigger automatic build and deployment.
The article examines the microapp architecture pattern—derived from microservices—to modularize mobile codebases, accelerate build and test cycles, and improve team autonomy, while also discussing its foundations, challenges, trade‑offs, and practical adoption steps.
This guide explains Jira's planning and tracking features, provides step‑by‑step instructions for installing the Data Center version, details initial configuration, demonstrates project and module creation, and shows how to integrate Jira with Jenkins and GitLab for automated CI/CD workflows.
In a seven‑day sprint, Nanguo Film transformed its entire streaming platform by moving over 30 systems to Alibaba Cloud's Serverless Application Engine, cutting operational effort by 70%, reducing costs by more than 40%, and achieving ten‑fold faster scaling while maintaining zero downtime.
The article explains test orchestration as a coordinated, automated testing workflow that enhances software quality and delivery speed by eliminating manual errors, integrating with CI/CD pipelines, and leveraging tools such as Ansible, Jenkins, and Kubernetes to streamline testing processes across DevOps environments.
This article explains the principles of agile development, outlines typical agile workflows and case studies, and then provides a comprehensive overview of the cloud native technology stack, including application definition, orchestration, runtime, provisioning, platform, observability, and serverless components, illustrating how modern IT teams can transition from traditional practices.
The article describes an intelligent grading and risk‑assessment framework for commercial platforms that unifies process control, feature mining, data collection, storage, strategy management, and annotation, enabling automated testing conversion with 94% accuracy, 90% recall, 8% conversion uplift, and surfacing dozens of bugs while supporting scalable, configurable deployment.
This article presents a detailed case study of the "Hummingbird" DevOps platform built by Zhongtai Securities' R&D team, describing its background, architecture, CI/CD pipeline, integration with tools like JIRA, container management, automated testing, monitoring, and the measurable efficiency gains achieved across development, testing, and production.
iQIYI integrated JaCoCo with its DevOps pipeline, using Git diff and Jira‑linked branch naming to automatically generate fine‑grained coverage reports at incremental, branch, and requirement levels, enforcing 90 % thresholds that lifted backend service coverage from under 70 % to over 90 % and markedly improved reliability.
The article explains how agile development and DevOps extend beyond coding to cover the entire application lifecycle, how containers and Kubernetes enable seamless collaboration between developers and operations, and why microservice architecture and Conway's law are essential for building scalable, cloud‑native systems.
The article explains how adopting automation and continuous testing—through appropriate tools, metric tracking, containerization, transparent communication, multi‑layer and performance testing—accelerates error detection, improves software quality, and enables faster, reliable releases in modern DevOps pipelines.
This article introduces the Jenkins Deploy Dashboard plugin, explains its purpose for visualizing deployment status across environments, and provides step‑by‑step instructions—including adding deployments to the dashboard, creating the dashboard view, and adding deployment buttons—using both scripted and declarative pipelines.
This article outlines the essential categories of DevOps tools—from planning and issue tracking to source control, build, test, CI/CD, configuration management, cloud platforms, container orchestration, monitoring, communication, and knowledge sharing—explaining why each is vital and listing popular examples for teams seeking efficient delivery pipelines.
This guide explains how to set up SonarQube and Sonar‑scanner for static code analysis, run the scanner with project parameters, install the Sonar‑GitLab plugin, configure commit‑status integration, and use the resulting GitLab commit status to enforce merge‑request policies based on pipeline outcomes.
This article introduces Jenkins Pipeline fundamentals, explains stages, nodes, and steps, compares Declarative and Scripted syntaxes, and provides detailed code examples for Windows, Docker, and Git operations to illustrate building, testing, and deploying applications.
This article explains the concept of progressive delivery, its industrial origins, how cloud‑native tools like Kubernetes, Traefik and Spinnaker enable automated A/B testing, canary and gray releases, and the practical benefits for developers, operations, and product teams when releasing features to millions of users.
Learn how to install Jenkins inside Docker using the jenkinsci/blueocean image, configure ports and volumes, unlock the instance, set up credentials for Git and SSH, create a multi‑branch pipeline with Blue Ocean, and write a Jenkinsfile that automates build, test, and deployment steps.
This article explains how to use Tekton, a cloud‑native CI/CD framework, to sync its component images to a Tencent Cloud container registry, generate an image‑mapping JSON, and deploy Tekton via GitHub Actions, Python scripts, and Kubernetes resources.
The article explains the critical differences between traditional test automation and continuous testing, detailing how continuous testing, integration, delivery, and deployment enhance software quality, speed, and team efficiency within a DevOps environment.
This article chronicles a recent graduate’s year‑long journey mastering cloud‑native technologies, detailing the design and implementation of a multi‑cluster Kubernetes architecture, unified logging, CI/CD pipelines, service governance with Istio, and private deployment strategies for a 3D editor platform.
This article explains how Spinnaker enables continuous delivery in Kubernetes environments by describing its role, deployment workflow, micro‑service architecture, pipeline design across DEV and UAT namespaces, and practical best‑practice recommendations for secure and efficient CD operations.
The article introduces major updates to the Taro React Native open‑source project, including a new react‑native template, GitHub Actions integration for automated builds, a Taro Playground app for debugging, and detailed CI/CD configurations to lower entry barriers for mobile app development.
This guide explains how to upload build artifacts to external repositories by using Nexus API for Maven artifacts and GitLab's generic package registry, covering authentication methods, required parameters, curl commands, and CI/CD job examples for automated publishing.
This guide explains how to store, upload, and retrieve build artifacts using Nexus repository manager through its UI, Maven configuration, Jenkins Nexus Artifact Uploader plugin, custom pipeline functions, and direct REST API calls, including download examples with curl and wget.
This article presents a comprehensive overview of serverless application DevOps, covering the definition, benefits, common use cases, development workflow, container image deployment, CI/CD pipelines with AWS SAM, security strategies, monitoring tools, and real‑world examples such as Coca‑Cola.
This article explains how GitLab CI/CD can be used to run continuous integration, trigger downstream pipelines across multiple projects, pass variables and specify branches, with practical code examples for microservice‑based architectures and guidance on pipeline visualization and permissions.
This article explains how to configure protected environments and manual approval jobs in GitLab CI/CD pipelines to control production deployments, illustrates YAML examples for deployment protection and approval stages, and introduces GitOps concepts and their benefits for modern cloud‑native infrastructure management.
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 guide explains how to set up a Gerrit instance, configure SSH keys and permissions, install the Gerrit Trigger plugin in Jenkins, and create a Jenkins pipeline that automatically runs when a review is merged, providing a complete end‑to‑end CI/CD workflow.
The article explains how Google’s continuous delivery practices—such as modular architecture, feature flags, gray‑scale deployments, rapid feedback loops, and a culture of always‑ready‑to‑deploy—enable faster, safer software releases while reducing risk and cost.
The article explains how Google treats development speed as a team sport, using modular architecture, continuous integration, feature flags, gray deployments, production‑like testing, and data‑driven decisions to enable frequent, small releases that improve quality, reduce risk, and lower costs.
This article analyzes why our Kubernetes clusters were constantly unstable—citing an erratic release process, missing monitoring, logging, documentation, and unclear request routing—and presents a comprehensive solution that includes a Kubernetes‑centric CI/CD pipeline, federated monitoring, centralized logging, a documentation hub, and integrated traffic management.
This guide explains how to create repository‑specific and global GitLab server hooks that validate commit messages against a custom pattern, showing step‑by‑step configuration, a Go pre‑receive script, and verification commands to ensure only properly formatted commits are accepted.
The article analyzes the instability of a company's Kubernetes clusters, identifies root causes such as an unstable release process, lack of monitoring, logging, documentation, and unclear request routing, and proposes comprehensive solutions including a Kubernetes‑centric CI/CD pipeline, a federated Prometheus monitoring platform, an Elasticsearch logging system, a centralized documentation hub, and a unified traffic management architecture.
This guide walks through installing Docker on CentOS 7, pulling the official Jenkins image, creating a host volume, running the container with proper port and volume mappings, retrieving the initial admin password, and completing the Jenkins setup with recommended plugins.
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 explains how Kaniko, a Google‑open‑source tool, enables building and pushing container images without a privileged Docker daemon by comparing traditional Docker methods, highlighting security concerns, and providing a step‑by‑step demonstration with commands and verification in a Kubernetes‑friendly environment.
This article analyzes why a company's Kubernetes clusters were constantly on the brink of failure and presents a comprehensive solution covering CI/CD pipeline reconstruction, federated monitoring with Prometheus, centralized logging via Elasticsearch, documentation centralization, and clarified request routing to achieve high reliability.
This article demonstrates how to set up a GitLab CI pipeline trigger token, use curl or Postman to invoke the pipeline via API, embed the trigger in .gitlab-ci.yml, and pass custom variables to the job, with example scripts and best‑practice tips.
This tutorial explains HTTP fundamentals, shows how to install and configure the Jenkins Generic Webhook Trigger plugin, and demonstrates parsing GET, POST, and header parameters using curl, Postman, and Jenkinsfile Groovy scripts for automated CI/CD pipelines.
This article details the full migration of a large‑scale mobile app from React Native 0.51 to 0.62, covering background, major improvements such as Hermes engine adoption, extensive performance testing, risk‑controlled batch rollout, API compatibility handling, tooling support, CI/CD integration, and post‑deployment verification.
GitOps automates infrastructure management by applying DevOps best practices such as version control, pull requests, and CI/CD pipelines to declarative infrastructure code, enabling reliable, observable, and secure deployments especially in Kubernetes‑based cloud‑native environments.
This article demonstrates how to build CI and CD pipelines for microservices using Jenkins, GitLab webhooks, and GitOps, covering repository structures, pipeline stages, code snippets, and deployment automation with Helm, including environment configuration.
This article explains how automation drives DevOps practices by improving speed, consistency, and reliability across the software lifecycle, discusses tools and challenges, and outlines future trends for integrating automated testing and infrastructure-as-code in modern development operations.
Over the past year, the author chronicles a hands‑on journey from a fresh graduate to a cloud‑native specialist, detailing the design and implementation of an enterprise‑grade Kubernetes architecture—including multi‑cluster logging, CI/CD pipelines, Istio service mesh, monitoring, and private‑deployment strategies—while sharing practical lessons learned.
This article outlines Baidu's evolution of build practices, presenting a group-level continuous delivery pipeline solution that includes a dual-engine ecosystem—standard plugin engine and non-standard containerized engine—and describes the intelligent build platform that enables dynamic, policy-driven, resource-efficient software delivery.
The article analyzes why a company's clusters were unstable—unstable release process, missing monitoring and logging, insufficient documentation, and unclear request routing—and proposes a comprehensive solution built around Kubernetes‑centric CI/CD, a federated Prometheus monitoring platform, Elasticsearch logging, centralized documentation, and Kong/Istio traffic management.
This article explains why complex applications benefit from ChatOps during development and testing, describes how to integrate CI/CD pipelines with instant‑messaging platforms, outlines tool selections such as Helm and Spinnaker, and shows how fast‑debugging tools like Nocalhost streamline the workflow.
The APP DIFF automated testing solution, presented at iQIYI’s i Technology Conference, combines deep‑link navigation, mock data services, and the AUI image‑diff algorithm within the Uiautomator2 framework to stabilize UI automation, cut execution time, achieve near‑human verification quality, and deliver significant coverage and cost savings across iQIYI mobile products.
This article explains what GitOps is, its core principles such as declarative configuration and versioned state, the operational benefits it brings—including improved visibility, productivity, reliability, and security—and provides step‑by‑step guidance on implementing GitOps workflows for cloud‑native applications.
This article describes Trip.com’s experience adapting its Android app to Android 11, covering background, key changes such as scoped storage and package visibility, migration strategies, implementation details, encountered challenges, and lessons learned for mobile developers.
The article chronicles a SaaS team's evolution from a two‑person monolithic application to a microservice‑based, containerized architecture, detailing API design, CI/CD practices, Spring Cloud and Kubernetes integration, automated deployment, tracing, and monitoring strategies.
This guide explains how to install and configure the Jenkins Active Choice Parameter plugin, create Groovy scripts for dynamic build options, debug GitLab API calls with curl or Postman, and implement both basic and optimized Groovy code to retrieve project branches and tags using stored Jenkins credentials.
This article demonstrates how to create unit tests for .NET Core methods using xUnit, measure code coverage with Coverlet, generate readable reports with ReportGenerator, and automate testing and coverage analysis in Azure DevOps pipelines, while also showing how to display project badges.
This article explains why observability is essential for DevOps, outlines four key practices—including production‑environment monitoring, structured logging, a DevOps‑focused culture, and pre‑deployment observability with remote debugging—to help teams detect, diagnose, and prevent issues throughout the software lifecycle.
This tutorial explains how to use Jenkins to integrate command‑line tools and webhooks for automating GitLab branch creation, covering API discovery, Postman testing, pipeline scripting, credential handling, shared library implementation, and final system configuration.
This guide explains what Tekton is, outlines its core CRDs, shows how to deploy it on a Kubernetes cluster, and provides a step‑by‑step example that builds, containers, and deploys a Spring Boot application using Maven, Docker, and Tekton pipelines.
This article explains the fundamentals of CI/CD and pipelines, identifies eight common anti‑patterns such as lack of code‑as‑pipeline, slow execution, unstable results, misuse of production data, excessive complexity, tight coupling, zombie pipelines, and manual intervention, and provides practical causes and remediation strategies for each.
This guide explains how to configure GitHub Actions to automatically synchronize GitHub repositories with Gitee, covering the basics of GitHub Actions, synchronization methods, action selection or creation, required preparation steps, workflow syntax, and practical code examples.
This article describes how a logistics company tackled the growing complexity of mobile app testing by evaluating automation tools, creating a real‑device platform, and implementing a Jenkins‑driven automation framework that supports parallel execution, script management, and future AI‑enhanced compatibility testing.
This article examines Netflix’s open‑source Spinnaker platform, detailing its microservice architecture, GitHub‑based code management, GitHub Actions continuous‑integration workflow, and Halyard‑driven deployment process, including sample build.yml and version.yaml configurations, offering practical insights for cloud‑native DevOps implementations.
After two years of migrating from Ansible to Kubernetes, we share the hard‑won lessons on why we moved, the challenges of operating a production cluster, decisions on monitoring, logging, CI/CD, security, cost, and how we built an internal platform to streamline development.
This guide explains how to configure Jenkins to connect to both same‑cluster and cross‑cluster Kubernetes environments, covering role bindings, network ports, certificate generation, Kubernetes cloud settings, pod template configuration, and testing via freestyle and pipeline jobs.
When you join a new software development team, asking the right 20 questions about technical setup, collaboration practices, external constraints, and product strategy helps you integrate quickly, avoid pitfalls, and contribute effectively from day one.
This guide walks through automating a Go project's build, handling private repository credentials, and deploying the compiled binary to a remote server using a Jenkins pipeline, covering project structure, build steps, credential management, and a complete pipeline script.
The article emphasizes that a CI/CD pipeline must be the exclusive route for deploying immutable artifacts to production, warning against direct local deployments, highlighting risks of lost traceability, and urging strict network-level controls to ensure only the pipeline can release code.
This guide walks through a systematic approach to creating, designing, architecting, and operating technical products for developers, covering product design, architecture diagrams, project organization, Git workflows, documentation, CI/CD pipelines, collaboration mechanisms, and post‑release maintenance to help teams deliver successful developer‑focused tools.
This article shares a comprehensive methodology for creating, designing, managing, documenting, and operating technical products—especially front‑end tools—by covering product design, architecture, project organization, collaboration, documentation, website generation, and demand handling, all drawn from real‑world experience.
The article explains that the primary goal of unit, integration, and functional testing is to increase confidence in each new release, advocating fully automated test suites managed by CI/CD pipelines that run on every deployment and pull request, while discouraging manual test execution.
A global cybersecurity firm replaced its fragmented cron‑based build, test, and deployment processes with an automated Jenkins CI/CD pipeline, integrating GitLab, Docker, and monitoring tools to achieve continuous delivery, visibility, and faster, reliable releases across multiple projects.
This article traces the evolution of software architecture from monolithic applications through vertical splitting and distributed services to modern microservice architectures, examines their advantages and drawbacks, and outlines a comprehensive technology stack—including service discovery, API gateways, authentication, logging, containerization, orchestration, and CI/CD tools—essential for building scalable, resilient systems.
This article walks through setting up GitLab CI to automatically build a Spring Boot JAR, create Docker images for Java 8 and Java 11, push them to a private registry, and deploy them to a server, covering required Dockerfiles, .gitlab-ci.yml configuration, environment files, and necessary GitLab variables.
This guide explains how Serverless Devs detects online changes to prevent deployment conflicts in Alibaba Cloud Function Compute, covering three scenarios—new resources, updates after online changes, and redeploying existing resources—while providing step‑by‑step experiments and a non‑interactive CI flag.
This article explains how Jenkins, the popular open‑source CI/CD tool, can be deployed and scaled using standalone servers, master‑agent configurations, and cloud‑native Kubernetes clusters, highlighting benefits such as automatic scaling, parallel builds, and cost‑effective resource utilization.
This article explains why a dedicated frontend build platform is needed, describes its core capabilities such as automated build, pluggable pipelines, audit‑based release, and external plugin exposure, and details the Docker‑in‑Docker architecture, process‑pool design, and sample Node.js code for a scalable CI/CD solution.
This article provides a step‑by‑step tutorial on building a DevOps pipeline that integrates Docker, Jenkins, GitLab, Maven, and SpringBoot, covering environment setup on CentOS, Maven pom configuration, Dockerfile creation, shell scripting for image building, multi‑machine deployment, and practical Jenkins job configuration.
This article explains how ZheZhe leverages Jenkins as an open‑source, plugin‑rich CI scheduler to classify projects, manage unified build scripts and config files, orchestrate job creation, execution, and cleanup, and scale a mixed Linux/macOS build farm supporting thousands of daily compilations.
This article chronicles a SaaS company's evolution from a two‑person monolithic Java application to a containerized microservice ecosystem using Spring Cloud, Kubernetes, Jenkins, and automated testing, highlighting practical decisions on API design, CI/CD pipelines, service splitting, and operational monitoring for small teams.
This guide explains the origins of GitOps, introduces Argo CD’s architecture and core concepts, and provides step‑by‑step instructions for installing, configuring, and operating Argo CD on Kubernetes, including CLI usage, cluster registration, application creation, synchronization, and health monitoring.
This tutorial shows how to refactor a Tekton‑based CI/CD pipeline by extracting Helm chart templates into a separate repository, configuring an Argo CD AppProject and Application, adding sync and manifest‑update tasks, customizing health checks, and finally achieving a streamlined GitOps workflow on Kubernetes.
To accelerate CI/CD pipelines, the article recommends using self‑hosted GitLab Runners on a private cloud to eliminate network bottlenecks, caching build dependencies locally, employing lightweight Alpine images for faster container pulls, and limiting job execution to changed files via the only:changes directive.
This article explains Jenkins declarative pipeline syntax, showing how to define pipelines, agents, stages, and steps with code examples—including simple and Docker‑based pipelines—and describes optional elements such as environment variables, options, tools, triggers, parameters, and post‑actions, providing a practical guide for DevOps practitioners.
This article details NetEase Cloud Commerce's journey of building a comprehensive SaaS quality assurance system—covering business challenges, goal setting, methodology, automation, visualization, and measurable improvements—to sustain fast iteration and high‑availability service delivery.
Google’s open‑source security tool, OpenSSF Scorecards, now at version 2.0, automates risk assessment for thousands of projects by providing pass/fail checks, binary‑artifact analysis, dependency verification, and CI/CD token controls, helping organizations identify vulnerable code, malicious contributors, and unsafe dependencies.
This article provides a comprehensive overview of Argo CD, a Kubernetes‑native GitOps continuous deployment tool, covering its architecture, core components, supported manifest types, key features, installation steps, cluster configuration, application creation, and synchronization methods using both CLI and UI.
This article introduces and compares fourteen widely used Jenkins alternatives—including BuildMaster, Microtica, GitLab, CircleCI, Bamboo, TravisCI, Semaphore, Buddy, Drone.io, GoCD, TeamCity, Buildkite, and Zuul—highlighting their key features, project URLs, and typical use cases for modern CI/CD pipelines.
Learn how to configure a Jenkins single‑branch pipeline to accept a branch name as a parameter, enabling dynamic code checkout by setting up a String parameter, using ${BranchName} in the pipeline script, and handling potential Lightweight checkout errors.
Effective artifact management and comprehensive version control are essential for CI/CD pipelines, ensuring that all source code, build scripts, configuration files, test data, database schemas, and infrastructure definitions are tracked, auditable, and reproducible across any environment.
This article traces the evolution of software architecture from monolithic applications through vertical splitting, distributed services, and SOA to modern microservices, and then details the essential technology stack—including service communication, API gateways, authentication, fault tolerance, logging, configuration, containers, orchestration, and CI/CD—required to build scalable, resilient cloud‑native systems.
The article emphasizes that a well‑designed CI/CD pipeline should automate the entire build and deployment process into a single command or script, enabling new developers to produce deployable artifacts quickly, while warning against excessive manual steps that hinder efficiency.
DevOps combines development and operations into a unified lifecycle—continuous development, integration, testing, feedback, monitoring, deployment, and maintenance—offering faster delivery, improved collaboration, automated processes, and higher software quality, with tools such as Git, Jenkins, Docker, and Ansible supporting each phase.
This article explains the origins of DevOps, its evolution from agile practices, and how containers and Kubernetes enable a seamless, automated pipeline—from code checkout and build to testing, code analysis, artifact storage, image creation, and staged deployment—illustrated with real‑world Jenkins pipelines and logs.
This article explains the DevOps lifecycle—its definition, advantages, and seven continuous phases (development, integration, testing, feedback, monitoring, deployment, and operations)—and shows how automation and collaboration between development and IT operations accelerate high‑quality software delivery.
The article explains how to design DevOps pipelines with quality thresholds that allow individual feature branches to be tested, scanned, and selectively deployed or rolled back, emphasizing short‑lived branches, trunk‑based development, and feature toggles to avoid the problems of long‑lived feature branches.
The article explains why artifacts should be built only once and treated as immutable, using containers as the ideal vehicle, and warns against the anti‑pattern of rebuilding from source code at each pipeline stage, which slows pipelines and creates inconsistent production releases.
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.
