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 | qimsdk-smartvenc_1.0.4-0qli+staging2 | |
|
binary_artifacts
Lookup:
|
Binary package | libqimsdk-smartvenc-dev_1.0.4-0qli+staging2_arm64 | |
| Binary package | libqimsdk-smartvenc1-dbgsym_1.0.4-0qli+staging2_arm64 | ||
| Binary package | libqimsdk-smartvenc1_1.0.4-0qli+staging2_arm64 |
No artifacts produced.
No output data.
Work requests that must be completed before this one can run.
| 125794 | 1 day, 15 hours | Server | copy to 1768, 1768, 1768, 1768, 1762, 1764 | 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.