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.
No artifacts produced.
No output data.
Work requests that must be completed before this one can run.
| 7874 | 2 months, 1 week | Server | copy to 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768, 1768 | 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.