Skip to content
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

Closed
imjasonh opened this issue Nov 21, 2018 · 4 comments
Closed

Document migration from BuildTemplate+Build to Task+TaskRun #250

imjasonh opened this issue Nov 21, 2018 · 4 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. meaty-juicy-coding-work This task is mostly about implementation!!! And docs and tests of course but that's a given

Comments

@imjasonh
Copy link
Member

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 a Task (stateless, parameterized resources which are invoked), and a Build is roughly equivalent to a TaskRun (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 a Task from a pre-defined TaskRun (#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.

@bobcatfish bobcatfish added this to the 0.3 Alpha release milestone Nov 21, 2018
@bobcatfish bobcatfish added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. meaty-juicy-coding-work This task is mostly about implementation!!! And docs and tests of course but that's a given labels Nov 30, 2018
@bobcatfish
Copy link
Collaborator

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

@shashwathi
Copy link
Contributor

/assign @shashwathi

@bobcatfish bobcatfish added okr This is for some internal Google project tracking and removed okr This is for some internal Google project tracking labels Feb 21, 2019
@bobcatfish bobcatfish removed this from the Pipelines 0.2 🎉 🎉 🎉 milestone Apr 25, 2019
@vdemeester
Copy link
Member

I think we are good closing this one, https://github.com/tektoncd/pipeline/blob/master/docs/migrating-from-knative-build.md is there, and knative/build is "long gone" 👼

/close

@tekton-robot
Copy link
Collaborator

@vdemeester: Closing this issue.

In response to this:

I think we are good closing this one, https://github.com/tektoncd/pipeline/blob/master/docs/migrating-from-knative-build.md is there, and knative/build is "long gone" 👼

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. meaty-juicy-coding-work This task is mostly about implementation!!! And docs and tests of course but that's a given
Projects
None yet
Development

No branches or pull requests

5 participants