You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That I can use multiple instances of a task that writes to the workspace volume, but to different paths.
E.g. one git-clone task that clone the app-code-repository and another git-clone task that clone the app-config-repository and that I in a later task can use files from both git-clone tasks.
Another use case is to git-clone code into a directory of workspace volume, and in addition fetch cached dependencies from a GCS bucket into another directory of the workspace volume.
Actual Behavior
This can currently be done using two workspaces of type PersistentVolumeClaim in combination with different values of subPath, e.g.
but when using a workspace of type volumeClaimTemplate there is currently no way of doing this, since providing two templates gives you two different volumes
If we add the field subPath to the WorkspacePipelineTaskBinding - different instances of a task can be bound to different subdirectories of the workspace volume. Then this is done when the pipeline binds the workspace to the instance of the task in the Pipeline.
Expected Behavior
That I can use multiple instances of a task that writes to the workspace volume, but to different paths.
E.g. one git-clone task that clone the app-code-repository and another git-clone task that clone the app-config-repository and that I in a later task can use files from both git-clone tasks.
Another use case is to git-clone code into a directory of workspace volume, and in addition fetch cached dependencies from a GCS bucket into another directory of the workspace volume.
Actual Behavior
This can currently be done using two workspaces of type
PersistentVolumeClaim
in combination with different values ofsubPath
, e.g.but when using a workspace of type
volumeClaimTemplate
there is currently no way of doing this, since providing two templates gives you two different volumesProposed Solution
If we add the field
subPath
to theWorkspacePipelineTaskBinding
- different instances of a task can be bound to different subdirectories of the workspace volume. Then this is done when the pipeline binds the workspace to the instance of the task in thePipeline
.Example
Pipeline
/kind feature
The text was updated successfully, but these errors were encountered: