Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand workspace support to pipelines and pipelineruns #1802

Closed
ghost opened this issue Jan 3, 2020 · 2 comments
Closed

Expand workspace support to pipelines and pipelineruns #1802

ghost opened this issue Jan 3, 2020 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ghost
Copy link

ghost commented Jan 3, 2020

Expected Behavior

Workspaces should be declarable in a pipeline and bindable in a pipelinerun. Threading a workspace through multiple tasks should allow for files to be shared across those tasks (if using the correct volume source types - PVC, configmap, secret).

We may also want to explore some kind of "from" syntax - a PipelineTask could declare that it wants the workspace "from" a prior pipeline task and Tekton would be responsible for exposing whatever volume source backs that workspace to both tasks.

Actual Behavior

At the moment we don't have any of the workspace types implemented for pipelines or pipelineruns.

This is a follow-on task from #1438

@ghost ghost added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 3, 2020
@bobcatfish bobcatfish assigned ghost Jan 6, 2020
@bobcatfish bobcatfish added this to the Pipelines 0.10 🐱 milestone Jan 6, 2020
@vdemeester
Copy link
Member

@sbwsg #1866 being merged, I guess this could be closed ?

@ghost
Copy link
Author

ghost commented Jan 22, 2020

👍 yes indeed!

@ghost ghost closed this as completed Jan 22, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants