Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jenkins Bitbucket Plugin - Triggers the pipeline even when repo is not configured with webhook

Bitbucket Plugin - Triggers the Jenkins pipeline even when the repo is not configured with webhook. This happening only when we are using two or more different repos in the pipeline.


We have two Bitbucket repos A and B one for hosting Codes and another one for hosting Build and Deployment scripts. (Devops related)

  1. Jenkins Pipeline - Configured to use Jenkinsfile from SCM in our case Repo A and Branch develop
  2. Jenkinsfile in turn will clone the Repo B for build and deployments scripts while pipeline is running using checkout step
  3. Repo A is configured with Webhook and Repo B is not configured with Webhook.

Steps to Reproduce:

  1. Commit something in the develop branch of Repo A and its trigger the pipeline as expected. No issue.
  2. Commit Something in the Repo B. No triggers since it was not configured with Webhook and its expected no issue.
  3. Now Commit something in the different branch of Repo A and its trigger the pipeline since there is change in the Repo B. I verified this in the Bitbucket Webhook log.

What we are expecting:

Whenever there is a change in develop branch of Repo A it can trigger the pipeline. But it should not trigger the pipeline for other Branches for Repo A or other Repos itself.

FYI, JIRA Ticket raised in Jenkins too.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events