Skip to content

docs: Document Bitbucket license requirement for groups#2471

Merged
chmouel merged 1 commit intotektoncd:mainfrom
tricktron:f-licensed-user-doc
Feb 11, 2026
Merged

docs: Document Bitbucket license requirement for groups#2471
chmouel merged 1 commit intotektoncd:mainfrom
tricktron:f-licensed-user-doc

Conversation

@tricktron
Copy link
Copy Markdown
Contributor

@tricktron tricktron commented Feb 11, 2026

📝 Description of the Change

Bitbucket Datacenter requires service account users to have LICENSED_USER permission for group-based access checks. Without it, users with group-only permissions cannot trigger builds.

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

Fixes #2468

🚀 Type of Change

  • 🐛 Bug fix (fix:)
  • ✨ New feature (feat:)
  • 💥 Breaking change (feat!:, fix!:)
  • 📚 Documentation update (docs:)
  • ⚙️ Chore (chore:)
  • 💅 Refactor (refactor:)
  • 🔧 Enhancement (enhance:)
  • 📦 Dependency update (deps:)

🧪 Testing Strategy

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

🤖 AI Assistance

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

If you have used AI assistance, please provide the following details:

Which LLM was used?

  • GitHub Copilot
  • ChatGPT (OpenAI)
  • Claude (Anthropic)
  • Cursor
  • Gemini (Google)
  • Other: ____________

Extent of AI Assistance:

  • Documentation and research only
  • Unit tests or E2E tests only
  • Code generation (parts of the code)
  • Full code generation (most of the PR)
  • PR description and comments
  • Commit message(s)

Important

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: Gemini gemini@google.com
Co-authored-by: ChatGPT noreply@chatgpt.com
Co-authored-by: Claude noreply@anthropic.com
Co-authored-by: Cursor noreply@cursor.com
Co-authored-by: Copilot Copilot@users.noreply.github.com

**💡You can use the script ./hack/add-llm-coauthor.sh to automatically add
these co-author trailers to your commits.

✅ 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

@gemini-code-assist
Copy link
Copy Markdown

gemini-code-assist bot commented Feb 11, 2026

Summary of Changes

Hello @tricktron, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Bitbucket Datacenter installation documentation by adding crucial information regarding license requirements for service account users. This update aims to prevent issues where users with group-only permissions might be unable to trigger builds due to missing LICENSED_USER global permission, providing a clear explanation and a workaround.

Highlights

  • Bitbucket Datacenter License Requirement: Added a new informational hint to the Bitbucket Datacenter installation documentation, clarifying that service account users must possess the LICENSED_USER global permission for group-based access checks to function correctly. This addresses issues where users with group-only permissions might fail to trigger builds without this license.
Changelog
  • docs/content/docs/install/bitbucket_datacenter.md
    • Added a new informational hint about the LICENSED_USER global permission requirement for service account users in Bitbucket Datacenter to ensure group-based access checks work correctly.
Activity
  • The pull request author, tricktron, created this PR to address a documentation gap related to Bitbucket Datacenter.
  • The PR is categorized as a documentation update (docs: type of change).
  • The author confirmed that no AI assistance was used in the creation of this pull request.
  • The author has completed several checklist items, including ensuring clear commit messages and updating documentation.
  • This pull request fixes GitHub issue Bitbucket Data Center: PAC Service Account User must be a Licensed User #2468.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Feb 11, 2026
View reviewed changes
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 adds important documentation about a license requirement for Bitbucket Data Center. The added note clarifies that the service account needs to be a licensed user for group-based permissions to work correctly. My feedback includes a suggestion to make the wording more concise and clear for better readability.

@tricktron
docs: Document Bitbucket license requirement for groups
54d29df 
Bitbucket Datacenter requires service account users to have
`LICENSED_USER` permission for group-based access checks. Without it,
users with group-only permissions cannot trigger builds.
@chmouel
Copy link
Copy Markdown
Member

chmouel commented Feb 11, 2026

/ok-to-test

@pipelines-as-code
Copy link
Copy Markdown

pipelines-as-code bot commented Feb 11, 2026

🔍 PR Lint Feedback

Note: This automated check helps ensure your PR follows our contribution guidelines.

⚠️ Items that need attention:

🤖 AI attribution

The following commits lack an explicit AI attribution footer:

  • 54d29df docs: Document Bitbucket license requirement for groups

If no AI assistance was used for a commit, you can ignore this warning.
Otherwise add an Assisted-by: or Co-authored-by: footer referencing the AI used.

ℹ️ Next Steps

  • Review and address the items above
  • Push new commits to update this PR
  • This comment will be automatically updated when issues are resolved
🔧 Admin Tools (click to expand)

Automated Issue/Ticket Creation:

  • /issue-create - Generate a GitHub issue from this PR content using AI
  • /jira-create - Create a SRVKP Jira ticket from this PR content using AI

⚠️ Important: Always review and edit generated content before finalizing tickets/issues.
The AI-generated content should be used as a starting point and may need adjustments.

These commands are available to maintainers and will post the generated content as PR comments for review.

🤖 This feedback was generated automatically by the PR CI system

@pipelines-as-code pipelines-as-code bot added bitbucket-datacenter doc documentation Improvements or additions to documentation labels Feb 11, 2026
@chmouel chmouel merged commit 0ca9063 into tektoncd:main Feb 11, 2026
5 checks passed
@chmouel
Copy link
Copy Markdown
Member

chmouel commented Feb 11, 2026

thank you 🙏🏻

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

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

bitbucket-datacenter doc documentation Improvements or additions to documentation

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Bitbucket Data Center: PAC Service Account User must be a Licensed User

2 participants

@tricktron @chmouel