Skip to content

[WIP]verify Azure Pipelines works with Bitbucket provider #309

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.

Sign up for GitHub

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

Open
xinredhat wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[WIP]verify Azure Pipelines works with Bitbucket provider #309

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 1 addition & 50 deletions integration-tests/config/testplan.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,57 +4,8 @@
"name": "backend-tests",
"templates": ["go"],
"tssc": [{
"git": "github",
"ci": "tekton",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
},
{
"git": "gitlab",
"ci": "tekton",
"registry": "nexus",
"tpa": "remote",
"acs": "remote"
},
{
"git": "gitlab",
"ci": "gitlabci",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
},
{
"git": "github",
"ci": "githubactions",
"registry": "artifactory",
"tpa": "remote",
"acs": "remote"
},
{
"git": "github",
"ci": "azure",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
},
{
"git": "github",
"ci": "jenkins",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
},
{
"git": "gitlab",
"ci": "jenkins",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
},
{
"git": "bitbucket",
"ci": "jenkins",
"ci": "azure",
"registry": "quay",
"tpa": "remote",
"acs": "remote"
Comment on lines 6 to 11

@qodo-code-review qodo-code-review Bot Feb 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Test matrix collapsed 🐞 Bug ⛯ Reliability

The default integration test plan now generates only 1 template×TSSC combination (go ×
bitbucket+azure), which significantly reduces CI coverage for other supported Git/CI/registry
combinations and increases regression risk.
Agent Prompt 
## Issue description
`integration-tests/config/testplan.json` currently defines only one `tssc` configuration (bitbucket+azure) and one template (go). Because the Tekton `tssc-e2e` task uses this file by default, CI will only generate and run a single project configuration, reducing coverage for other supported provider combinations.

## Issue Context
- The CI task downloads this file when no `testplan` param is provided.
- `TestPlan` expands `templates × tssc` into the Playwright project matrix.

## Fix Focus Areas
- integration-tests/config/testplan.json[1-16]
- integration-tests/tasks/tssc-e2e.yaml[58-73]
- src/playwright/testplan.ts[64-93]

## Suggested fix approach
- Option A (simplest): Re-add the previously covered `tssc` combinations into the existing `backend-tests` plan and keep the new `bitbucket+azure` entry alongside them.
- Option B: Add a new dedicated plan (e.g., `bitbucket-azure-tests`) for the focused verification, while keeping `backend-tests` as the broad matrix used by default.
- If you choose Option B and want Tekton to run the new plan, ensure the execution path can select it (e.g., by passing a custom testplan content via the Tekton `testplan` param, or adjusting the command used in the task/scripts to allow overriding the plan name).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Expand Down