Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
jenkins: 2.204.1, absi-plugin: 1.0.3
-
-
1.1.0
Description
After configuring everything like described on https://community.atlassian.com/t5/Bitbucket-articles/Atlassian-supported-Jenkins-integration-for-Bitbucket-Server/ba-p/1148326 , I get the same behavior as described by Kevin Reynolds: the trigger is executed in bitbucket, receives a 200 back from Jenkins, but no build is started.
In the Jenkins logs I see:
Payload: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent@1b554079 Received refs changed event from repo: JG/bitbucket-sonarqube-integration
I've debugged the code and traced it down to the getScms method in BitbucketWebhookConsumer returning an empty collection.
Tracing further why it's empty, I end up in the implementation in
which shows it needs at least a completed build to return a non empty collection.
I feel this should rather use (from script console)
Jenkins.instance.getItem('bitbucket-sonarqube-integration').definition.scm
which returns a BitbucketSCM instance as defined in the job definition.
Can easily be reproduced when removing all builds from a job.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
Hi Sven,
My initial read of the bug suggested this was likely the same root cause as JENKINS-60649- but doing a bit more investigation it looks like they have separate causes. Accordingly, I've reopened the ticket.
I see the same behavior. Exactly as if "Bitbucket Server trigger build after push" is not checked. This does not happen with freestyle projects, only with pipelines.
I see the webhooks coming in, but nothing triggered
-------------------
Payload: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent@117c02d
Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer
Received refs changed event from repo: HAL/dobby
Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer
--------------------
Also, sbv I'm assuming you saw the rest of the conversation in case of Kevin Reynolds. In his case, the "Bitbucket Server trigger build after push" option was not selected, and instead a similar sounding checkbox related to a different Bitbucket plugin (Bitbucket branch plugin? ) was selected.
Aidin F
added a comment - - edited I see the same behavior. Exactly as if "Bitbucket Server trigger build after push" is not checked. This does not happen with freestyle projects, only with pipelines.
I see the webhooks coming in, but nothing triggered
-------------------
Payload: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent@117c02d
Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer
Received refs changed event from repo: HAL/dobby
Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer
--------------------
Also, sbv I'm assuming you saw the rest of the conversation in case of Kevin Reynolds. In his case, the "Bitbucket Server trigger build after push" option was not selected, and instead a similar sounding checkbox related to a different Bitbucket plugin (Bitbucket branch plugin? ) was selected.
mhenschke_atlassian: How is this a duplicate of
JENKINS-60649? That one is about the webhook not being created. This one is about the webhook not triggering the job. (I created the webhook manually, it fires, it returns an ok result, but no build is being run - all of which is not described inJENKINS-60649)