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

Bitbucket Plugin Jenkins - Job Triggers Even Though No Changes In Included Regions


I posted this on Jenkins too because I am not sure if the issue is in Jenkins or the Jenkins Bitbucket plugin or expected behaviour.  Jenkins jobs are triggering unexpectedly.

I have configured Bitbucket plugin for Jenkins and Webhook in Bitbucket Server.

Jenkins 2.319.1
BitBucket Plugin 1.1.11
BitBucket Server v7.17.1

I have Jenkins jobs configured for 

Build when a change is pushed to BitBucket

I have specified

Included Regions

and watching master branch

Day 1
Commit 1.  Merge Commit 1 into master with changed files in Included Regions.  The Jenkins job triggers as expected.

Day 2. 
Commit 2.  Merge Commit 2 into master.  Commit 2 has made no changes to any files in the Included Regions.   The Jenkins jobs triggers as if changes had been made to files in Included Regions.

I checked the webhook and the Request is sending a fromHash for Commit 1 and a toHash for Commit 2.   This appears correct.

The Jenkins job that triggers does a

git rev-list

back to Commit 1.    Is Jenkins/Bitbucket plugin looking at Commit 1 and re-executing the Jenkins job on Day 2 even though we now only care about Commit 2 on Day 2?   I would not expect the triggering changes associated with Commit 1 to cause the Jenkins job to execute again. 

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events