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 | fastrpc_1.0.6-1qli1 | |
|
binary_artifacts
Lookup:
|
Binary package | fastrpc-support-dbgsym_1.0.6-1qli1_arm64 | |
| Binary package | fastrpc-support_1.0.6-1qli1_arm64 | ||
| Binary package | fastrpc-tests-dbgsym_1.0.6-1qli1_arm64 | ||
| Binary package | fastrpc-tests_1.0.6-1qli1_arm64 | ||
| Binary package | libfastrpc-dev_1.0.6-1qli1_arm64 | ||
| Binary package | libfastrpc1-dbgsym_1.0.6-1qli1_arm64 | ||
| Binary package | libfastrpc1_1.0.6-1qli1_arm64 |
No artifacts produced.
No output data.
Work requests that must be completed before this one can run.
| 38964 | 1 month, 1 week | Server | copy to 463, 463, 463, 463, 463, 463, 463, 463, 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.