Glossary · Automation software engineering and architecture
Artifact repository
Also known as: Binary repository, Package repository
German: Artefakt-Repository
In software engineering, an artifact repository is a managed storage system for versioned build outputs such as compiled binaries, libraries, packages, container images and firmware files, together with their metadata. It provides a controlled source for deployment and reuse, separate from the source code repository.
- Software engineering
In one sentence
An artifact repository stores versioned build outputs such as binaries, packages and firmware images as a controlled source for deployment.
Example
The CI pipeline publishes every released PLC library and edge container image to the company's artifact repository, and field updates are only taken from there.
How it applies
- Engineering: Build pipelines publish Build artifact files to the repository; later stages and other projects pull them from there instead of rebuilding. This keeps what was tested identical to what is deployed.
- Operation and maintenance: Service teams download released firmware and software from one controlled location. Retention rules make older versions available for machines that stay in the field for decades.
- Documentation: Each released artifact should be traceable to its source revision, build configuration, test results and release notes. The documentation team can link manuals and release notes to artifact versions so readers know exactly which software a document describes.
Artifact repository vs. source code repository
A source code repository (version control) stores what developers write and its history. An artifact repository stores what the build produces. Artifacts should be immutable once published: a new build gets a new version rather than overwriting an old one.
Access control and integrity checks, such as checksums or signatures, protect the repository from tampered artifacts.