-
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
Document migration from BuildTemplate+Build to Task+TaskRun #250
Comments
I think this is unblocked now! But @shashwathi I'm guessing you're in a good position to take this on since you've migrated so many examples in #493 🙏 ? No worries tho if you'd rather not take it on :D |
/assign @shashwathi |
I think we are good closing this one, https://github.com/tektoncd/pipeline/blob/master/docs/migrating-from-knative-build.md is there, and /close |
@vdemeester: Closing this issue. 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. |
Related to #147
As a former Build user, it should be straightforward for me to migrate BuildTemplates and Builds I had previously defined to match the new model for Pipelines.
In the new model, a
BuildTemplate
is roughly equivalent to aTask
(stateless, parameterized resources which are invoked), and aBuild
is roughly equivalent to aTaskRun
(the running invocation, with state).There are some differences, particularly around how
Task
parameters are defined and passed into steps, and how currently you can only create aTask
from a pre-definedTaskRun
(#249).At a minimum we should document how to migrate to the new world, and ideally we would be able to write a script that transforms a Build YAML into a TaskRun YAML, likewise for BuildTemplate -> Task.
The text was updated successfully, but these errors were encountered: