Update suites once the items have been copied. We have to run this in the target workspace, which might not be the same as this workflow's workspace. That involves triggering a separate workflow using a well-known template.
| Label | Category | Name | |
|---|---|---|---|
|
source_artifact
Lookup:
|
Source package | userspace-resource-manager-extensions_0.3.9-0qcom+staging1~bpo13+1 | |
|
binary_artifacts
Lookup:
|
Binary package | userspace-resource-manager-extensions-dbgsym_0.3.9-0qcom+staging1~bpo13+1_arm64 | |
| Binary package | userspace-resource-manager-extensions_0.3.9-0qcom+staging1~bpo13+1_arm64 | ||
| Binary package | userspace-resource-manager-extensions-dbgsym_0.3.9-0qcom+staging1~bpo13+1_amd64 | ||
| Binary package | userspace-resource-manager-extensions_0.3.9-0qcom+staging1~bpo13+1_amd64 |
No artifacts produced.
No output data.
Work requests that must be completed before this one can run.
| 21123 | 1 month, 3 weeks | Server | copy to 1765, 1765, 1765, 1765, 1765 | Completed | Success |
This work request is not required by any other one.
{}
Task has not yet been configured.
Dynamic task data has not yet been computed.
{ "step": "trigger-update-suites", "display_name": "Start workflow to update repository indexes" }
{}
No output data.