You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have been integrated Jenkin with Bitbucket for my application.
In Jenkin side, I have added the configuration in "Build with BitBucket Push and Pull Request Plugin" Triggers while create and update.
In Bitbucket Cloud, I have added a web hook for JenkinUrl/bitbucket-ppr-hook, for triggering.
It works fine and I use to get build status (green tick or red cross) in every pull request raised or updated with new changes.
Now, for no reason, this status stopped showing and I didn't do any configuration changes from my end.
Any licensing issue ? Need to be in any specific plans ?
Can you please help on identifying the issue and fix it.
I'd like to ask a few questions so we can better help you:
1. Does a build get triggered in Jenkins, when an event specified in the Triggers of this webhook occurs?
I'm just trying to understand if the webhook does not get triggered at all, or if it does and it's just the status that is not showing.
2. If you open the Commits page of this repo on Bitbucket website, do you see a build status there for the commits of the PR's source branch (assuming that the builds get triggered)?
3. Do you see any statuses listed if you run the following API call for one of the affected PRs?
curl -u <Bitbucket_username>:<app-password> https://api.bitbucket.org/2.0/repositories/<workspace-id>/<repo-slug>/pullrequests/<pr-id>/statuses
<Bitbucket_username> your Bitbucket username
<app-password> either your Atlassian account's password or an app-password
<workspace-id> the workspace id of the workspace that contains this repo
<repo-slug> the repository's slug
<pr-id> the id of the PR, which you can find in the URL of the PR when you open it on Bitbucket website