Try to fire the hook for refs/pull-requests/.*/merge

Question

Try to fire the hook for refs/pull-requests/.*/merge

dzwicker opened this issue 6 years ago · 4 comments

Bitbucket creates a commit for every PR where the PR is already merged. The ref for this commit is refs/pull-requests/<pr-number>/merge. I have created a rule

"4bba60c1-710a-449e-8481-1704fb4aa0d5": {
        "regex": "refs/(pull-requests/.*)/merge",
        "target": "eservice_backend_EServiceV3prTest_GradleBuildUnitTest",
        "type": "build",
        "triggerOnEmptyBranches": true,
        "triggerOnPullRequest": false,
        "cancelRunningBuilds": false,
        "triggerInclusion": "",
        "triggerExclusion": "",
        "downStreamTriggerType": "build",
        "downStreamTriggerDescription": "",
        "downStreamTriggerTarget": ""
    }

But this seams not to work.

Answer 1 · 2019-01-08T13:46:53.000Z

Are the branch definitions set in tenacity?

…

On Tue, 8 Jan 2019, 14:31 Daniel Zwicker ***@***.*** wrote: Bitbucket creates a commit for every PR where the PR is already merged. The ref for this commit is refs/pull-requests/<pr-number>/merge. I have created a rule "4bba60c1-710a-449e-8481-1704fb4aa0d5": { "regex": "refs/(pull-requests/.*)/merge", "target": "eservice_backend_EServiceV3prTest_GradleBuildUnitTest", "type": "build", "triggerOnEmptyBranches": true, "triggerOnPullRequest": false, "cancelRunningBuilds": false, "triggerInclusion": "", "triggerExclusion": "", "downStreamTriggerType": "build", "downStreamTriggerDescription": "", "downStreamTriggerTarget": "" } But this seams not to work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#56>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_jyLvASxDavCS97cOba8lyqSMkO5A-ks5vBI-FgaJpZM4Z1Yf1> .

Answer 2 · 2019-01-09T08:08:04.000Z

yes, branch defs in TC are set. In TC i can trigger the branch manually.

Can this be a problem of this special branch. It is only managed by bitbucket. The user pushes its feature branch and creates a PR and bitbucket create/updates the refs/pull-requests/<pr-number>/merge.

So the listeners of the plugin are not notified?

Answer 3 · 2019-01-09T08:52:21.000Z

are u able to make it work with any other type of branch? the hook contains some logging (Trigger From Ref:, postReceive: etc), if you enable the debug switch you might be able to confirm that the listener is triggered, if not then bitbucket does not support this kind of branch. we usually just have a rule to the target branch

…

On Wed, Jan 9, 2019 at 10:08 AM Daniel Zwicker ***@***.***> wrote: yes, branch defs in TC are set. In TC i can trigger the branch manually. Can this be a problem of this special branch. It is only managed by bitbucket. The user pushes its feature branch and creates a PR and bitbucket create/updates the refs/pull-requests/<pr-number>/merge. So the listeners of the plugin are not notified? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_jyKV5-OuW4JatL9aaHmugBY4DoMefks5vBaNkgaJpZM4Z1Yf1> .

Answer 4 · 2019-01-09T14:11:05.000Z

Ok. bitbucket doesn't trigger the plugin for this kind of branches