repo:push to master events do not trigger builds about bitbucket-push-and-pull-request-plugin HOT 13 CLOSED

@gmarzot do you have some news? The version 2 of the plugin was released yesterday, maybe is the problem solved in the new version?

from bitbucket-push-and-pull-request-plugin.

Hi I'm facing same issue but for feature branches repo:push to feature events do not trigger builds.

Can you help on how to solve it.

Plugin-Version: 2.0.0
Jenkins-Version: 2.176.1

jenkins log:

Should schedule job : true and (polling result has changes false or is pull request false)

It's working fine for Master and PR.

from bitbucket-push-and-pull-request-plugin.

@vweng @arohithr8 please, can you test the bitbucket-push-and-pull-request-2.1.0-beta-3 version and let me know if it works for you? Thank you

from bitbucket-push-and-pull-request-plugin.

@cdelmonte-zg Thanks for adding the triggerAlsoIfNothingChanged option, I can confirm it works with the following settings:

bitBucketTrigger([[$class: 'BitBucketPPRRepositoryTriggerFilter', actionFilter: [$class: 'BitBucketPPRRepositoryPushActionFilter', triggerAlsoIfNothingChanged: true, triggerAlsoIfTagPush: false]]])

from bitbucket-push-and-pull-request-plugin.

Might you provide more context?
Thanks

from bitbucket-push-and-pull-request-plugin.

not sure what additional info is needed. I ended up hacking the code to get it to work for us.
diff attached. I was not able to fully inspect the changes tracked by the event in the plugin code.. but it appeared to consider them "INSIGNIFICANT" despite the event being caused by a substantive merge/push to origin/master

I dont think my code change is correct but am not sure how this plugin determines the 'changes' metric from the bitbucket webhook payload.

repo_push_diff.txt

from bitbucket-push-and-pull-request-plugin.

Hi @gmarzot,
I'll check the diff, thank you for sharing it.

One question, did you try to configure the push allowed branches simply with 'master' instead than '*/master'?

There were some changes in the plugin to allow regex etc. in the style of the git plugin and the screenshot in the documentation was updated only today...

from bitbucket-push-and-pull-request-plugin.

I believe we tried it both ways... but it looked like the allowed branch test was passing fine.

that line was coming back false
boolean hasChanges = pollingResult.hasChanges();

I don't know why pollingResult is in the picture at all.. isn't all the necessary info in the webhook payload?

from bitbucket-push-and-pull-request-plugin.

Hi @gmarzot, pollingResult.hasChanges() method isn't part of the plugin, but it's coming from here

We are using it on the push events, to be sure, that we are triggering a job only in case of a change in the related repository/branch.

To be sure that changes between remote and local branch exist, you could check the diffs between the pertinent remote branch on the bitbucket cloud server and the correlated local branch on the Jenkins server using git status or something similar from the shell of the server where Jenkins is running on...

Let me know

from bitbucket-push-and-pull-request-plugin.

We're facing exactly same issue. Please remove the pollingResult.hasChanges() check, as it always return false with feature branch pushes. It's working fine for master and PR though.

Plugin-Version: 2.0.0
Jenkins-Version: 2.190.1

from bitbucket-push-and-pull-request-plugin.

So this is same bug as #54

from bitbucket-push-and-pull-request-plugin.

@cdelmonte-zg Thank you, after updating to version 2.2 and adding triggerAlsoIfNothingChanged: true as @vweng mentioned above it's working as expected.

from bitbucket-push-and-pull-request-plugin.

Thank you all, I updated just now the readme file.

from bitbucket-push-and-pull-request-plugin.