Description of problem:

Bitbucket Cloud webhook processing experiences severe performance degradation (49+ seconds) on repositories with large commit histories. The webhook controller uses a paginated API endpoint (GetCommits) that iterates through the   

entire commit history to fetch commit information, causing significant delays for repositories with thousands of commits.

This impacts pipeline trigger responsiveness and user experience when using Pipelines-as-Code with Bitbucket Cloud repositories.                                                                                h3. Prerequisites (if any, like setup, operators/versions):                                                                                                                                                                              

  * Pipelines-as-Code with Bitbucket Cloud provider enabled                                                                                                                                                                                  

  * Bitbucket Cloud repository with 1000+ commits                                                                                                                                                                                            

  * Webhook configured for push events

Prerequisites (if any, like setup, operators/versions):

  * Pipelines-as-Code with Bitbucket Cloud provider enabled

  * Bitbucket Cloud repository with 1000+ commits                                                      

  * Webhook configured for push events

Steps to Reproduce

  # Configure Pipelines-as-Code with Bitbucket Cloud provider                                    

  # Set up webhook on a repository with 2000+ commits

  # Push a commit to trigger the webhook                               

  # Observe webhook processing time in controller logs

Actual results:

• Paginates through entire commit history
• Fetches all commits until finding the target SHA

• Causes linear time complexity O where n = total commits

• Results in multiple API calls and significant network overhead

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *