-
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
Cut PipelineResources from some examples #4971
Conversation
/lgtm |
/test pull-tekton-pipeline-alpha-integration-tests |
closes #4375 |
docs/tasks.md
Outdated
@@ -34,8 +34,6 @@ weight: 200 | |||
- [Substituting in `Script` blocks](#substituting-in-script-blocks) | |||
- [Code examples](#code-examples) | |||
- [Building and pushing a Docker image](#building-and-pushing-a-docker-image) | |||
- [Mounting multiple `Volumes`](#mounting-multiple-volumes) |
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.
Can we wait until we have approval on tektoncd/community#720?
What is the best practice to configure |
/retest |
/test pull-tekton-pipeline-alpha-integration-tests |
@@ -83,7 +83,7 @@ A `Pipeline` definition supports the following fields: | |||
- [`tasks`](#adding-tasks-to-the-pipeline) - Specifies the `Tasks` that comprise the `Pipeline` | |||
and the details of their execution. | |||
- Optional: | |||
- [`resources`](#specifying-resources) - **alpha only** Specifies | |||
- [`resources`](#specifying-resources) - **deprecated** Specifies |
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.
🎉
docs/tasks.md
Outdated
type: Socket | ||
``` | ||
|
||
#### Mounting multiple `Volumes` |
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.
As long as the feature is still there perhaps we shouldn't fully remove this docs, but alter them to say that while this is possible, it is not recommended unless in use cases where no alternative exists.
Thanks for this @lbernick. |
Thanks @afrittoli and @pritidesai, I think I'll make this PR just PipelineResources for now |
This commit replaces PipelineResources with workspaces in documentation examples not related to those features. PipelineResources are deprecated, so our documentation shouldn't be using them as examples unless it is necessary. It also cuts the example related to reusing a Task with different PipelineResources (as the recommended way to do this would be with params). Lastly, it encourages users to reference the community catalog, rather than examples tests, for examples of Tasks, because many examples tests either make use of PipelineResources or aren't realistic.
Ok, should be ready for re-review |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
This commit replaces PipelineResources with workspaces in documentation examples
not related to those features. PipelineResources are deprecated, so our documentation shouldn't be
using them as examples unless it is necessary.
It also cuts the example related to reusing a Task with different
PipelineResources (as the recommended way to do this would be with params).
Lastly, it encourages users to reference the community catalog, rather
than examples tests, for examples of Tasks, because many examples tests
either make use of PipelineResources or aren't realistic.
/kind documentation
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