-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Introduce workspaces to Pipelines. #1866
Conversation
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, AFAIK though I think you still need an owner's review.
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/meow
/cc @bobcatfish
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following is the coverage report on pkg/.
|
A workspace can be threaded through the tasks of a Pipeline, allowing easier reuse and customisation of shared storage between tasks. Workspace types have been added to Pipeline structs: * A Pipeline declares a list of workspace names that it requires be provided by a PipelineRun. * A PipelineTask declares a mapping from a Pipeline's workspace name to a workspace name declared by the Task it references (or embeds). * A PipelineRun declares the concrete workspace implementations - whether they be a PVC, emptyDir, configMap or secret - and passes those in with the name declared by the Pipeline it references (or embeds). An example PipelineRun has been added to demonstrate usage of the workspaces in pipelines. Outstanding TODOs: * Add tests
OK, barring any last build failures or reviewer items I think this PR is in a finished state. |
The following is the coverage report on pkg/.
|
nicely done @sbwsg 👍 /lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/meow
🎉
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierretasci, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
🙏 thank you! |
A workspace can be threaded through the tasks of a Pipeline, allowing easier
reuse and customisation of shared storage between tasks.
Workspace types have been added to Pipeline structs:
by a PipelineRun.
workspace name declared by the Task it references (or embeds).
they be a PVC, emptyDir, configMap or secret - and passes those in with
the name declared by the Pipeline it references (or embeds).
An example PipelineRun has been added to demonstrate usage of
workspaces in pipelines but I still need to add docs and tests.
TODOs:
runAfter
for now.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes