Gray testing, also known as canary release, lets you roll out a new feature to a small, controlled group of users first—like a chef serving a daring new pizza to a few trusted diners—so you can gather real feedback, control risk, and gradually expand to all users once stability is proven.
This step‑by‑step tutorial shows how to obtain your InstallShield license key, create the required license.lic file, install or update InstallShield with the license, and verify activation using the command‑line tool, ensuring your build environment is properly licensed.
This article compares the three common Windows installer formats—MSI, EXE, and MSIXBundle—detailing their features, advantages, disadvantages, typical use cases, and providing guidance on which format best fits personal, enterprise, or developer scenarios.
The article outlines ten frequent pitfalls that organizations encounter when adopting DevOps—such as out‑of‑order delivery, misinterpreting DevOps roles, neglecting database automation, and ignoring security—and provides practical guidance on planning, collaboration, and balanced speed‑quality trade‑offs to achieve successful DevOps outcomes.
This article explains continuous delivery (CD) within DevOps, describing its definition, automated workflow, key benefits such as reduced risk, faster releases, higher quality, flexibility and cost savings, as well as common implementation challenges and best‑practice recommendations.
This article details Industrial and Commercial Bank of China's journey to standardize continuous delivery, outlining the background challenges, the definition of release units, the construction of a standardized toolchain, implementation results, and future plans to enhance DevOps performance across the enterprise.
Continuous delivery ensures rapid, safe code deployment by automating testing and mirroring production environments, outlining its concept, goals, principles, prerequisites, mandatory standards, recommended practices, and key metrics to achieve frequent, stable product releases.
This guide explains how beginners and experienced developers can discover, download, install, and run open‑source projects from GitHub, covering release pages, official sites, online demos, Chinese documentation, package managers, services deployment, and troubleshooting tips.
This article explains what gray release (canary deployment) is, why it is needed to reduce risk and improve product quality, and provides a step‑by‑step guide covering strategy, user targeting, data feedback, rollback, deployment architectures, and version management for modern software operations.
The article explains the challenges of API version control, introduces canary release as an alternative deployment strategy, and illustrates its practical implementation at ING Bank, highlighting benefits such as gradual rollout, easy rollback, and improved stability for continuously evolving APIs.
Continuous delivery is a practice that enables rapid, safe, and automated software releases, reducing deployment pain by encouraging frequent, small changes, automating pipelines, fostering self‑service, visibility, and reliability, with examples and lessons drawn from Netflix’s implementation and its impact on developer productivity.
This article explains the challenges of traditional enterprise IT delivery, outlines the role of DevOps and continuous delivery, and presents a detailed case study of a large financial firm that achieved six‑fold deployment speed gains through standardized pipelines, artifact management, and automated cross‑team notifications.
Microsoft unveiled winget, an open‑source Windows Package Manager, at Build 2020, detailing its command‑line tool for searching, installing, and managing software, its roadmap toward v1.0 release in May 2021, and how developers and ISVs can leverage it for streamlined app distribution.
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 several release‑management patterns—project release, release‑window, release‑train, and continuous delivery—describing their advantages, drawbacks, and how they can be combined to accelerate high‑quality software delivery in large, inter‑dependent systems.
Monolithic architecture, built as a single deployable unit, offers rapid development, simple deployment, and easy scaling via load balancers, but as applications grow, it introduces codebase complexity, slower IDEs, deployment challenges, limited scalability, and technology lock‑in, prompting many teams to consider microservices.
This article explores common release management models—project release, release windows, release trains, and continuous delivery—detailing their advantages, drawbacks, and implementation techniques, and offers strategies for combining these approaches to accelerate high‑quality software delivery in large, complex systems.
This article explains how teams can adopt continuous delivery by first mapping their existing workflow, defining a clear "done" criteria, establishing a regular release cadence, and fostering a culture of empathy, humility, and accountability, while also highlighting automation opportunities and real‑world examples.
In this talk, Ctrip’s R&D Director Wu Yiting shares how the company’s continuous delivery platform evolved through large‑scale platform launches, major reforms, and the aftermath of the 528 incident, highlighting improvements in security, availability, scalability, and container‑based delivery 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.
The article explains Google’s internal Midas Package Manager (MPM), detailing its build definition files, immutable and mutable metadata stored in Bigtable, distributed replication via Colossus, client‑side pull and P2P copying, as well as its access‑control, encryption, and signing mechanisms that enable massive, conflict‑free software deployment at Google’s scale.
This article explains Docker containers as software shipping boxes that standardize environments, solve dependency and scaling challenges, and offer a lightweight alternative to virtual machines for efficient, isolated deployment across many servers.
The article recounts how a decades‑old, unused code path was unintentionally re‑activated during a rushed deployment of the Retail Liquidity Program, leading Knight Capital to send erroneous orders that caused a $460 million loss and the firm’s bankruptcy.
