Skip to content

Introduction into Deployment

This section defines the key notions of deployment.

Terminology

Deployment

A deployment is the controlled process of making a specific version of software, configuration, or infrastructure change available in a target environment (for example, development, staging, or production).

A deployment typically includes:

  • Selecting a specific package or version
  • Transferring it to the target system(s)
  • Applying configuration and environment-specific settings
  • Executing installation or update steps
  • Verifying that the system is running as expected after the change

In other words, deployment describes the end-to-end process of delivering and activating changes in an environment.

Installation

An installation is the technical act of placing a package’s contents onto a system and making them usable by the operating system or runtime environment.

Installation usually involves:

  • Copying files to specific locations
  • Registering services or binaries
  • Setting permissions
  • Executing install or setup scripts

Installation focuses on what happens on a single system, not on the broader rollout or release process.

Deployment vs. Installation

Although closely related, deployment and installation are not the same:

  • Installation is a technical step: it describes how a package is installed on a system.
  • Deployment is a process: it may include one or more installations, along with preparation, configuration, validation, and rollback considerations.

A deployment can involve:

  • Installing a new package
  • Updating an existing installation
  • Reconfiguring a service without installing new software
  • Coordinating changes across multiple systems

In short:

  • You install a package
  • You deploy a change

Package

A package is a bundled, distributable unit that contains software components and, optionally, metadata such as version information, dependencies, scripts, or configuration templates.

A package may include:

  • Application binaries or artefacts
  • Configuration defaults
  • Installation or upgrade scripts
  • Dependency definitions

Packages are created to ensure that software can be distributed and deployed in a consistent and repeatable way.

Version

A version is a unique identifier assigned to a specific state of a package, application, or configuration at a particular point in time. Versions are typically expressed using numbers, labels, or a combination of both (for example, 1.4.2, 2026.02, or release-2026-02-15), depending on the versioning scheme in use.

  • A package version identifies the exact contents of a package
  • A deployed version indicates which package or configuration state is currently active in an environment

Deployment Procedures

....

Changelog

Date Author Message
2026-02-26 aresnikowa qc-0: How to reuse content