add bitcket+jenkins test

[xinredhat]

Summary by CodeRabbit

• Tests
  • Expanded test coverage with an additional test scenario configuration combining Bitbucket, Jenkins, Quay registry, and remote tooling integrations.

[coderabbitai]

Walkthrough

A new test configuration entry has been added to the tssc array in integration-tests/config/testplan.json with git: bitbucket, ci: jenkins, registry: quay, tpa: remote, and acs: remote, expanding the test matrix by one scenario.

Changes

Cohort / File(s)	Summary
Test Configuration Addition integration-tests/config/testplan.json	Added a new tssc test scenario combining Bitbucket git provider with Jenkins CI, Quay registry, and remote TPA/ACS deployments

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Add BitBucket back to testplan for CI #108: Adds a nearly identical Bitbucket + Jenkins configuration entry to the same tssc array, suggesting potential consolidation or sequential test matrix expansion.
• Add GitLabCI testplan.json #109: Also extends the tssc test matrix with a different git/CI provider combination, indicating ongoing test coverage improvements.
• Remove bitbucket as git provider #152: Manages Bitbucket-related test entries in the same configuration file, relevant for test scenario consistency.

Suggested labels

configuration, testing

Suggested reviewers

• jkopriva
• chetna14manku

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "add bitcket+jenkins test" clearly conveys the primary change: adding a new test configuration that combines bitbucket as the git provider with jenkins as the CI system. The title is directly related to the changeset, which adds a new test scenario entry to the testplan.json file with those exact specifications. While there is a spelling error ("bitcket" should be "bitbucket"), the intent remains clear and unambiguous—a developer scanning the repository history would immediately understand that this PR introduces a bitbucket+jenkins test combination. The title is concise and avoids unnecessary noise, making it suitable as a summary of the main change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 20de65e and 3e2535d.

📒 Files selected for processing (1)

• integration-tests/config/testplan.json (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-10-08T10:25:55.812Z

Learnt from: CR
PR: redhat-appstudio/tssc-test#0
File: README.md:0-0
Timestamp: 2025-10-08T10:25:55.812Z
Learning: Applies to testplan.json : Place testplan.json at the repository root and define templates, tssc combinations, and tests arrays per the documented schema

Applied to files:

• integration-tests/config/testplan.json

🔇 Additional comments (1)

integration-tests/config/testplan.json (1)

52-58: New test matrix combination added successfully.

The new bitbucket + jenkins configuration fills a gap in the test matrix. The JSON structure is consistent with existing entries, and there are no obvious duplicates within the tssc array.

Please verify that:

1. The test infrastructure supports the bitbucket + jenkins combination
2. All necessary fixtures and mocks for bitbucket webhooks and Jenkins pipelines are in place

I can help verify this by searching for existing bitbucket + jenkins test handlers. Would you like me to run a verification script?

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[konflux-ci-qe-bot]

@xinredhat: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name	Status	Rerun command	Build Log	Test Log
e2e-4.19-fqh49	Failed	/retest	View Pipeline Log	View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/rhtap-team/rhtap-cli:e2e-4.19-fqh49

Test results analysis

<not enabled>

OCI Artifact Browser URL

<not enabled>