jenkins: 2.204.1, absi-plugin: 1.0.3
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:
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)
which returns a BitbucketSCM instance as defined in the job definition.
Can easily be reproduced when removing all builds from a job.