-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
2
-
False
-
-
False
-
-
Story (Required)
The Gitea-based e2e tests (resolvers_gitea_test.go) exist in tektoncd/pipeline but are not included in any CI job. These tests use the build tag `//go:build e2e && gitea`, which means they are excluded from normal `-tags=e2e` runs and never get executed in CI.
This task covers adding CI configuration to run these tests as part of the
tektoncd/pipeline e2e matrix.
Background (Required)
<Describes the context or background related to this story>
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)
- Gitea e2e tests (TestGitResolver_HTTPAuth, TestGitResolver_API, TestGitResolver_API_Identifier) run in tektoncd/pipeline CI on every PR
- Existing e2e test jobs (stable, beta, alpha) are not affected
- A Makefile target is available for running Gitea tests locally
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