When a reusable workflow is called twice in the same workflow in parallel, it may require a dedicated network to run (for instance if it spawns services) and will always require unique volumes to mount the workdir and the env. There really is no way to guarantee a unique name derived from the job name etc. Instead, a random name is set and used as a base for both the internal volumes and the dedicated network (if any). |
||
|---|---|---|
| .. | ||
| artifactcache | ||
| cacheproxy | ||
| common | ||
| container | ||
| exprparser | ||
| filecollector | ||
| jobparser | ||
| lookpath | ||
| model | ||
| runner | ||
| schema | ||
| workflowpattern | ||