Summary

Configure OAuth authentication for the Jenkins Bitbucket Branch Source Plugin to replace legacy authentication methods and improve security, maintainability, and long-term compatibility with Bitbucket Cloud.

Description

The Jenkins Bitbucket Branch Source Plugin currently relies on legacy authentication mechanisms for repository discovery, branch indexing, and pull request operations. This work will configure OAuth authentication using a Bitbucket OAuth Consumer and Jenkins Credentials to align with Bitbucket Cloud's recommended authentication model.

The implementation should:

• Configure a Bitbucket OAuth Consumer.

• Store the OAuth Client ID and Client Secret securely within Jenkins Credentials.

• Configure the Bitbucket Branch Source Plugin to use OAuth authentication.

• Validate repository indexing and branch discovery.

• Validate Multibranch Pipeline functionality.

• Validate Pull Request discovery and build triggers.

• Validate webhook integration.

• Confirm repository browsing and SCM checkout continue to function correctly.

• Update Jenkins documentation with the new authentication configuration.

Acceptance Criteria

• OAuth authentication is successfully configured for the Bitbucket Branch Source Plugin.

• Repository indexing completes successfully.

• Multibranch Pipeline jobs continue to discover branches and Pull Requests.

• SCM checkout succeeds using OAuth credentials.

• Existing Jenkins jobs continue to function without regression.

• Jenkins Credentials securely store the OAuth Client ID and Client Secret.

• Documentation has been updated to reflect the new authentication process.

Benefits

• Aligns with Bitbucket Cloud authentication best practices.

• Improves security by eliminating reliance on deprecated authentication methods.

• Centralizes credential management within Jenkins.

• Simplifies future credential rotation.

• Improves long-term supportability of Jenkins Bitbucket integrations.