-
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
Beta documentation: write up alternatives to PipelineResources if they remain Alpha #1369
Comments
This is part of documenting and providing Tasks in the catalog that would help user not using PipelineResource. Related to [tektoncd/pipeline#1369](tektoncd/pipeline#1369). Signed-off-by: Vincent Demeester <[email protected]>
This is part of documenting and providing Tasks in the catalog that would help user not using PipelineResource. Related to [tektoncd/pipeline#1369](tektoncd/pipeline#1369). Signed-off-by: Vincent Demeester <[email protected]>
This is part of documenting and providing Tasks in the catalog that would help user not using PipelineResource. Related to [tektoncd/pipeline#1369](tektoncd/pipeline#1369). Signed-off-by: Vincent Demeester <[email protected]>
This is part of documenting and providing Tasks in the catalog that would help user not using PipelineResource. Related to [tektoncd/pipeline#1369](tektoncd/pipeline#1369). Signed-off-by: Vincent Demeester <[email protected]>
@vdemeester can we add a must have for Beta to this issue? |
@vdemeester @afrittoli @dibyom and I discussed today: at the very least we should have a doc explaining the current state and weighing pros and cons of how you do things with and without PipelineResources |
Note we are also making progress with Task equivalents of PipelineResources in tektoncd/catalog#95 |
First version of migration doc now exists: https://github.com/tektoncd/pipeline/blob/master/docs/migrating-v1alpha1-to-v1beta1.md |
…n" docs This is part of providing documentation for alternative to pipeline resource. As we have now kubeconfig-creator task in the catalog as the replacement for cluster resource, Added the same in the "v1alpha1 to v1beta1 migration" docs. Ref: tektoncd#1369 Signed-off-by: Divyansh42 <[email protected]>
…n" docs This is part of providing documentation for alternative to pipeline resource. As we have now kubeconfig-creator task in the catalog as the replacement for cluster resource, Added the same in the "v1alpha1 to v1beta1 migration" docs. Ref: #1369 Signed-off-by: Divyansh42 <[email protected]>
Expected Behavior
Clearly documented approach to passing files, folders, docker images, cluster information, auth information, repo information etc etc without relying on PipelineResources.
Actual Behavior
At the moment our docs assume that PipelineResources are "the answer" to modelling meaningful resources external to the CI/CD system. In the most recent PipelineResource working group we landed on the idea of keeping PipelineResources as Alpha when the rest of the Tekton resources move to Beta. So with that approach we'll need to make sure that our docs correctly reflect the "right" way to work with external resources.
The text was updated successfully, but these errors were encountered: