Skip to content

chore: replace e2e env variables from server to data center#2666

Merged
zakisk merged 1 commit intotektoncd:mainfrom
zakisk:replace-remaining-bb-server-to-bbdc
Apr 9, 2026
Merged

chore: replace e2e env variables from server to data center#2666
zakisk merged 1 commit intotektoncd:mainfrom
zakisk:replace-remaining-bb-server-to-bbdc

Conversation

@zakisk
Copy link
Copy Markdown
Member

@zakisk zakisk commented Apr 9, 2026

this replaces all the env variables names from bitbucket server to data center.

📝 Description of the Change

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

  • Unit tests
  • Integration tests
  • End-to-end tests
  • Manual testing
  • Not Applicable

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

  • I have not used any AI assistance for this PR.
  • I have used AI assistance for this PR.

Important

Slop will be simply rejected, if you are using AI assistance you need to make sure you
understand the code generated and that it meets the project's standards. you
need at least know how to run the code and deploy it (if needed). See
startpaac to make it easy
to deploy and test your code changes.

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Claude noreply@anthropic.com

✅ Submitter Checklist

  • 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
  • ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
  • ♽ I have run make test and make lint locally to check for and fix any
    issues. For an efficient workflow, I have considered installing
    pre-commit and running pre-commit install to
    automate these checks.
  • 📖 I have added or updated documentation for any user-facing changes.
  • 🧪 I have added sufficient unit tests for my code changes.
  • 🎁 I have added end-to-end tests where feasible. See README for more details.
  • 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
  • If adding a provider feature, I have filled in the following and updated the provider documentation:
    • GitHub App
    • GitHub Webhook
    • Gitea/Forgejo
    • GitLab
    • Bitbucket Cloud
    • Bitbucket Data Center

this replaces all the env variables names from bitbucket
server to data center.

Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>
@chmouel
Copy link
Copy Markdown
Member

chmouel commented Apr 9, 2026

are you ready for the gh secret set and update infra repo?

@chmouel
Copy link
Copy Markdown
Member

chmouel commented Apr 9, 2026

/lgtm

Copy link
Copy Markdown

@pipelines-as-code pipelines-as-code bot left a comment

Choose a reason for hiding this comment

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

Congrats @zakisk your PR Has been approved 🎉

✅ Pull Request Approved

Approval Status:

  • Required Approvals: 1
  • Current Approvals: 1

👥 Reviewers Who Approved:

Reviewer Permission Level Approval Status
@chmouel admin

📝 Next Steps

  • Ensure all required checks pass
  • Comply with branch protection rules
  • Request a maintainer to merge using the /merge command (or merge it
    directly if you have repository permission).

Automated by the PAC Boussole 🧭

@zakisk zakisk merged commit 14a8e6b into tektoncd:main Apr 9, 2026
11 of 13 checks passed
@zakisk zakisk deleted the replace-remaining-bb-server-to-bbdc branch April 9, 2026 09:07
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request renames environment variables related to Bitbucket Data Center from TEST_BITBUCKET_SERVER_* to TEST_BITBUCKET_DATA_CENTER_* across documentation, tests, and configuration files to improve naming consistency. I have no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants