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 | linux-qcom-next_7.2.0+20260826-0qli~bpo13+1 | |
|
binary_artifacts
Lookup:
|
Binary package | linux-headers-7.2.0-qcom-next-20260826_7.2.0+20260826-0qli~bpo13+1_arm64 | |
| Binary package | linux-headers-qcom-next_7.2.0+20260826-0qli~bpo13+1_arm64 | ||
| Binary package | linux-image-7.2.0-qcom-next-20260826-dbg_7.2.0+20260826-0qli~bpo13+1_arm64 | ||
| Binary package | linux-image-7.2.0-qcom-next-20260826_7.2.0+20260826-0qli~bpo13+1_arm64 | ||
| Binary package | linux-image-qcom-next_7.2.0+20260826-0qli~bpo13+1_arm64 |
No artifacts produced.
No output data.
Work requests that must be completed before this one can run.
| 113242 | 1 week | Server | copy to 464, 464, 464, 464, 464, 464, 23, 24 | 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.