DigitalDownConverter — Deployment
Debian Packages
The pipeline is distributed as Debian packages built by CI and hosted in the MPIFR Aptly
repository. The edd_dbbc Docker image installs them at build time.
Package |
Contents |
|---|---|
|
Python library ( |
|
Compiled C++ binaries ( |
Docker Image
Property |
Value |
|---|---|
Image name |
|
Base image |
|
Ansible build role |
|
Registry |
|
The image installs python3-edd-core, python3-edd-dbbc, edd-dbbc-utils, mkrecv,
mksend, and psrdadacpp from the MPIFR Aptly repository.
CI Pipeline
Stage |
Job |
Description |
|---|---|---|
|
|
CMake + make, produces |
|
|
Builds Debian packages via |
|
|
CTest suite against built binaries |
|
|
Python test suite with coverage |
|
|
lcov C++ coverage badge |
|
|
Python coverage badge |
|
|
C++ style lint badge |
|
|
Python lint |
|
|
Uploads packages to Aptly (requires build + tests) |
|
|
Builds and pushes |
Ansible Deployment
The pipeline is deployed via the ddc_processor Ansible role:
ansible-playbook provision.yml --tags ddc_processor
The role delegates to EDD.core.common with:
image_name: edd_dbbc
default_container_name: ddc_processor
container_cmd: "edd_ddc_processor --host={{ edd_subnet }} --port={{ bind_port }}"
register_as_pipeline: True
provision_test_imports: "edd.dbbc.ddc_processor_tests"
Provision Tests
Provision tests are imported from edd.dbbc.ddc_processor_tests. They verify that the
pipeline starts, accepts configuration, and reaches the configured state before the
observation begins.