[JIRA] (JENKINS-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda commented on JENKINS-55517 Re: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes This is starting to become a bigger issue for us since keeping the Bitbucket Branch Source plugin at version 2.2.12 is now causing dependency issues with Blue Ocean (see picture below): For anyone else experiencing this problem, you might need to hold back on updating Blue Ocean as well until this issue is 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Change By: German Pineda Attachment: image-2019-01-30-08-34-53-641.png 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes Change By: German Pineda Environment: Jenkins: 2.150.1 LTSBitbucket Branch Source Plugin: 2.3.0 Pipeline Multibranch Plugin: 2.20 Installation: Windows 2016 Server (Used windows installer)Proxy: NoneBrowser: Chrome Version 71.0.3578.98 (Official Build) (64-bit) 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Change By: German Pineda Summary: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes
Title: Message Title German Pineda created an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes Issue Type: Bug Assignee: Unassigned Attachments: PRBuilds.PNG Components: bitbucket-branch-source-plugin Created: 2019-01-10 19:04 Environment: Jenkins: 2.150.1 LTS Bitbucket Branch Source Plugin: 2.3.0 Installation: Windows 2016 Server (Used windows installer) Proxy: None Browser: Chrome Version 71.0.3578.98 (Official Build) (64-bit) Labels: plugin Priority: Major Reporter: German Pineda I currently have a Bibucket Mercurial Multibranch pipeline that scans every 5 minutes for any PRs submitted against master which triggers our build for those branches. After updating our Bitbucket Branch Source plugin version from 2.2.12 to 2.2.15, some scans would periodically result in retriggering all of our PR builds even though none of those PRs were updated. This has a tremendous impact as all of our Jenkins agents would overload with unnecessary builds. I recently updated the Bitbucket Branch Source plugin version to 2.3.0 (most recent release) hoping this had been fixed and it's still a problem. This issue appears to have been introduced in version 2.2.13. I'm reverting back to 2.2.12 until this issue is fixed.
