- blhc
Workflow blhc
This workflow schedules Blhc tasks to analyze the logs from builds. A single Blhc is scheduled for each artifact.
task_data
:prefix
(string, optional): prefix this string to the item names provided in the internal collectionreference_prefix
(string, optional unlessenable_regression_tracking
is set): prefix for the item names provided in the internal collection in the corresponding workflow run for reference testssource_artifact
(Single lookup, optional unlessenable_regression_tracking
is set): the source artifact that the build logs are based onpackage_build_logs
(Multiple lookup, required): the debian:package-build-log artifacts to analyzeqa_suite
(Single lookup, optional unlessenable_regression_tracking
orupdate_qa_results
is True): the debian:suite collection that reference tests are being run against to detect regressionsreference_qa_results
(Single lookup, optional unlessenable_regression_tracking
orupdate_qa_results
is True): the debian:qa-results collection that contains the reference results of QA tasks to use to detect regressionsenable_regression_tracking
(boolean, defaults to False): configure the workflow to detect and display regressions in QA resultsupdate_qa_results
(boolean, defaults to False): when set to True, the workflow runs QA tasks and updates the collection passed inreference_qa_results
with the results.extra_flags
(optional): a list of command-line flags to be passed to each scheduled Blhc taskvendor
(string, required): the distribution vendor, used to buildenvironment
for Blhccodename
(string, required): the distribution codename, used to buildenvironment
for Blhcarch_all_host_architecture
(string, defaults toamd64
): concrete architecture on which to run tasks for binary packages withArchitecture: all
.
The workflow computes dynamic metadata as:
subject: distinct
source
field (separated by spaces) from each of the artifacts’ data
The lookup in package_build_logs
may result in , and in that case the workflow adds corresponding
dependencies. Promises must include source_package_name
and
source_package_version
fields in their data.