-
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
TEP-0108: Mapping Workspaces #4887
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
Hey @Aleromerog the code seems fine but I'll wait for @jerop to take a look as well. We should definitely document this feature though and add a release note about it. |
The following is the coverage report on the affected files.
|
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.
Thank you @Aleromerog!
Please add documentation and example for this feature
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-build-tests |
1 similar comment
/test pull-tekton-pipeline-build-tests |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
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.
Thanks @Aleromerog! 🎉
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop 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 |
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.
@Aleromerog one more request, please add an example that uses this feature - can be a modification of this example: https://github.com/tektoncd/pipeline/blob/main/examples/v1beta1/pipelineruns/workspaces.yaml
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, just a few nits and a +1 on Jerop's feedback
The following is the coverage report on the affected files.
|
/retest |
According to TEP-0108: auto-mapping Workspaces from Pipelines to PipelineTasks when the names of the Workspaces declared in the Pipeline and PipelineTask are the same to reduce verbosity and improve usability of Pipelines.
The following is the coverage report on the affected files.
|
/lgtm |
Marking TEP-0107 as implemented, thank you @Aleromerog! PR: tektoncd/pipeline#4887
Marking TEP-0107 as implemented, thank you @Aleromerog! PR: tektoncd/pipeline#4887
Marking TEP-0108 as implemented, thank you @Aleromerog! PR: tektoncd/pipeline#4887
Marking TEP-0108 as implemented, thank you @Aleromerog! PR: tektoncd/pipeline#4887
Changes
According to TEP-0108, auto-map Workspaces from Pipelines to PipelineTasks when the names of the Workspaces declared in the Pipeline and PipelineTask are the same to reduce verbosity and improve usability of Pipelines.
This PR makes sure to map workspace from PipelineTask if the name of the workspace match with the name of the workspace of the Pipeline.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes