[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Björn Seebeck commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered Our Jenkins is at 2.164.2, BB 5.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster updated JENKINS-55617 Tested with bitbucket-branch-source-plugin 2.4.4 - works as expected. Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Christoph Forster Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster updated JENKINS-55617 Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Christoph Forster Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster edited a comment on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered Tested with Jenkins 2.174, BB 5.9.1 and bitbucket-branch-source-plugin 2.4.4 - works as expected. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Björn Seebeck commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We get the same issue after updating from 2.2.12 to v2.4.4 of BB branch source plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Jakub Pawlinski commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered Oh, I added similar issue to https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/189 will update to v2.4.4 and confirm, thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered I think this has been fixed with v2.4.4 release. PR was https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/172 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Jakub Pawlinski Component/s: bitbucket-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel edited a comment on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We were also running into this issue and can't merge PRs if the PR was created before the branch build has finished. *In addition*, all builds of branches created from this PR branch are also added to this build list of the PR which totally crashes our development process (might link to https://issues.jenkins-ci.org/browse/JENKINS-55404). See: !InkedImage Pasted at 2019-4-2 12-35_LI.jpg|thumbnail! We are using Jenkins 2.164.1 and BB branch source plugin 2.4.2 and BB 6.1.2 with "Webhook to Jenkins for Bitbucket Server" PluginThank you in advance for the fix! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Thomas Kuchel Attachment: InkedImage Pasted at 2019-4-2 12-35_LI.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We were also running into this issue and can't merge PRs if the PR was created before the branch build has finished. In addition, all builds of branches created from this PR branch are also added to this build list of the PR which totally crashes our development process (might link to https://issues.jenkins-ci.org/browse/JENKINS-55404). See: We are using Jenkins 2.164.1 and BB branch source plugin 2.4.2 and BB 6.1.2 with "Webhook to Jenkins for Bitbucket Server" Plugin Thank you in advance for the fix! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Thomas Kuchel Attachment: InkedImage Pasted at 2019-4-2 12-35_LI.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Jakub Pawlinski commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We are affected as well. I intentionally postponed 2.4.0 update as we are using bitbucket/stash 4.5.2, but this problem exists on 2.2.16. It wasn't happening in 2.2.13 that we upgraded from. Thanks for workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Christoph Forster Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered When configuring "Discover Branches - All Braches" the problem can be avoided. Nevertheless it's not the desired behaviour (as I don't want branches to be listed when a PR exists) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Christoph Forster created an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Issue Type: Bug Assignee: Unassigned Attachments: image-2019-01-16-12-43-36-655.png Components: bitbucket-branch-source-plugin Created: 2019-01-16 11:48 Priority: Critical Reporter: Christoph Forster I'm using Jenkins 2.159 and bitbucket-branch-source-plugin 2.4.0. My Multibranch Pipeline Configuration is as followed: Discover Branches - Exclude branches that are also filed as PRs Discover pull requests from origin - The current pull reequest version Periodically scan multibranch pipeline triggers - Interval 2 minutes Let's assume I push a Feature branch to Bitbucket which causes the BRANCH to be build. When I create a Pull-Request on this branch the PR is also triggered as Job on Jenkins running on the same Git Commit ID. This leads on Bitbucket Side to 2 "Job Status" Informations The Problem now is, that the BRANCH Job is being disabled on Jenkins and NO Bitbucket Notification is send anymore - The Status remains on "In Progress". Now we can't merge our Pull Requests as Bitbucket says, that there is still a Build in Progress. This can only be solved by pushing another change to the branch so that the PR Job is getting retriggered.
