Andrew Bayer

Oh wait, https://github.com/tektoncd/resolution/blob/408cd52add36156c4cbbb0819404ea9daee1cfc2/pkg/reconciler/resolutionrequest/resourcerequest.go#L59-L61 - there is a global timeout of 1 minute currently for `ResolutionRequest`s, so we do specifically need `PipelineRun`/`TaskRun` reconciler logic to deal with that. I'll get on...

Ok, another thing Resolution needs - unit tests. The reconciler has none, so while I've verified that a `PipelineRun` will fail if the `ResolutionRequest` fails, I can't actually verify that...

@jerop and I chatted about the resolvers question on Friday - I'd advocate for moving the existing git and bundle resolvers into Pipeline, along with an eventual catalog resolver, since...

Oops, shouldn't have said `closes` on that PR - we haven't actually promoted to beta yet, we've just folded everything from https://github.com/tektoncd/resolution into the Pipeline repo and deployment. Reopening!

Interesting - that'll need new syntax for "this `Task` needs to be resolved, so here's where to find it based on its name/type/version (for the Hub) and the `Pipeline`'s resolution...

So this is a bunch of interesting questions! I'm pretty sure (I'm going to add e2e tests for this today) that if you've got a `resolver` reference for a `PipelineTask`...

(and down the road, it may make sense for a `PipelineRun` to be able to say "here are the default org/repo (or URL for the anonymous clone approach) and revision...

Also, I keep thinking that it may make sense to eventually add real fields (with relevant structs) to `ResolverRef` for the built-in resolvers, so that you can just do ```...

/wip /assign @jerop @pritidesai @dibyom @afrittoli @vdemeester (marking this as WIP because I want to get a good amount of test runs in to be sure it actually fixes the...

I cherry-picked this onto #5077, since I'm running the e2e tests over and over on there anyway to validate kind jobs, and in the 19 `*-integration-tests` jobs that have run...