Replacing PipelineResources in tutorial

[psschwei]

Currently, the Pipeline tutorial uses git and image PipelineResources for Task inputs/outputs see here. As there are beta-supported alternatives for both PipelineResources (for git, for image), it might be good to update the tutorial to use these alternatives.

[pritidesai]

/kind documentation

[rudeigerc]

Hi, I'd like to make an update. However, the entire tutorial used PipelineResource as the resource input and output.
Should the update be imported as a complement of the origin tutorial or a brand new one?

[pritidesai]

We could add as complementing to the original tutorial that way folks can compare a pipeline with and without resources. @psschwei would that work?

[psschwei]

@pritidesai I like the idea of including both alternatives. However, for a new user looking to get started with Tekton (which I assume is the main audience for the tutorial), would it be better to keep things simple and only present a single way of doing things?

[pritidesai]

Sure @psschwei sounds good.

How are we updating this section to replace pipeline resources? I am asking because this section refers to a task using pipeline resources to build an image. After replacing pipeline resources with the catalog tasks, it can no longer be represented as a single task instead it has to be converted to a pipeline to combine git-clone and kaniko or buildah catalog task 😞.

[vdemeester]

@pritidesai we would need to have a task that does all (the git-clone and the build). This means we wouldn't use a task from the catalog but it would work 👼🏼.

[psschwei]

@pritidesai we would need to have a task that does all (the git-clone and the build). This means we wouldn't use a task from the catalog but it would work 👼🏼.

Does it make sense to add a clone&build task to the catalog?

[vdemeester]

@pritidesai we would need to have a task that does all (the git-clone and the build). This means we wouldn't use a task from the catalog but it would work 👼🏼.

Does it make sense to add a clone&build task to the catalog?

I am less sure about that yet. Let's see a bit where discussions on tektoncd/community#316 and https://github.com/tektoncd/community/pull/318/files are going before 👼🏼 🙏🏼

[pritidesai]

I am less sure about that yet. Let's see a bit where discussions on tektoncd/community#316 and https://github.com/tektoncd/community/pull/318/files are going before 👼🏼 🙏🏼

Yup, I agree with @vdemeester, lets wait and see how the discussion unfolds on tektoncd/community#316 and tektoncd/community#318.

@psschwei you have hit this at the right time and I am hopeful we will find a solution to it.

[sbose78]

+1

We need to start having folks get used to the alternatives of PipelineResources sooner.

[psschwei]

Adding link to TEP-0044 now that it's merged. It includes a comparison with the TEP formerly known as 0046, which was closed.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[jerop]

/lifecycle frozen

we still need to do this to help users migrate off pipelineresources

[jeremyjjbrown]

The staleness of such an important ticket (and easy?) makes me pause on using this project.

[rebelopsio]

I’m currently working through learning Tekton from a newcomer’s perspective including making use of workspaces. I’d love to help get the documentation updated around this topic.

[dibyom]

Thanks @rebelopsio I think @geriom also has some ideas in this space.

[geriom]

I created an introductory tutorial last year. I'll make my priority to update it and get it merged this week.

That wasn't merged because we struggled to decide where that doc fits, in the end we decided to step back and rethink the docs strategy, we (the documentation working group) came up with a roadmap, new structure and new doc guidelines to make the overall documentation experience a lot better.

I'll open a bunch of issues with the proper context for every documentation item we have in mind. The idea is to have a good, friendly and educational documentation experience for the launch of pipelines v1.

[geriom]

Tracking these guides now in #4554 and #4555

[lbernick]

/assign geriom

Geri, sounds like you are working on this currently? feel free to remove your assignment if not.

[geriom]

@dibyom with #4789 merged I think we can close this issue. I'm don't have the permissions to do it.

[vdemeester]

/close
@geriom you should be able to close with the /close comment I think

[tekton-robot]

@vdemeester: Closing this issue.

In response to this:

/close
@geriom you should be able to close with the /close comment I think

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.