Story (Required)

As a tekton administrator, I want to be able to configure a timeout of greater than 1 minute for the git resolver for my users with huge repos

Background (Required)

In thread https://redhat-internal.slack.com/archives/C04PZ7H0VA8/p1722528561852009 the openshift/osde2e folks have repo big enough that git cloning can take more than one minute.

See both in repeated jobs in their namespace (while other namepaces with smaller repos worked fine) and will as personal clone by kpavic@redhat.com 

I found upstream issue https://github.com/tektoncd/pipeline/issues/6025 and that max timeout is noted in the doc at https://tekton.dev/docs/pipelines/git-resolver/#options

Looks like step one is simply allowing override in git-resolver-config configmap and the other configmaps but that will have to be vetted upstream.

Kruno was able to provide instructions for moving the test out of the big repo, and then git clone etc the big repo in the test.  Non-trivial work for the user, but

it is a workaround.

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met