Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13760

Too many notifications for release -> feature merge in Git plan branches

XMLWordPrintable

      Setup:

      • Bamboo tracks a git repository with master and feature branches
      • there is a branch plan for feature so that Bamboo should notify committers about test errors
      • someone merges master into feature to keep it up to date

      Expected behavior: the person performing the merge gets notification about any errors

      Actual behavior: everyone who had a commit in master which got merged (in practice this means the whole team) gets notification

      Notification is not the only affected component, e.g. the commit list in the "Changes" tab of the build detail view also contains all the commits.

            [BAM-13760] Too many notifications for release -> feature merge in Git plan branches

            James Dumay added a comment -

            Hi there,

            Atlassian is pleased to announce the release of Bamboo 5.5 which contains a resolution for this issue.

            This release is available to all customers with active licenses. Please be sure to read the release notes and upgrade guide for more information.

            Thanks,
            James Dumay
            Product Manager

            James Dumay added a comment - Hi there, Atlassian is pleased to announce the release of Bamboo 5.5 which contains a resolution for this issue. This release is available to all customers with active licenses. Please be sure to read the release notes and upgrade guide for more information. Thanks, James Dumay Product Manager

            Marcin Gardias added a comment -

            In Bamboo 5.5 we introduce new behavior: we detect which commits are 'local' to the branch and which come from other branches. In particular:

            • When using Mercurial, we check which branch a commit originates from.
            • When using Git we look at ancestry path: if change is on the ancestry path between previous and current revision, we consider it 'local'. The reason we use ancestry path is that branch information in git is lost when the branch head moves.

            Notifications are sent only to authors of 'local' changes.
            You can still see the changes from other branches on the build result screen, as we consider this useful feature, but they are marked with 'M' lozenge for easy distinction.

            Marcin Gardias added a comment - In Bamboo 5.5 we introduce new behavior: we detect which commits are 'local' to the branch and which come from other branches. In particular: When using Mercurial, we check which branch a commit originates from. When using Git we look at ancestry path: if change is on the ancestry path between previous and current revision, we consider it 'local'. The reason we use ancestry path is that branch information in git is lost when the branch head moves. Notifications are sent only to authors of 'local' changes. You can still see the changes from other branches on the build result screen, as we consider this useful feature, but they are marked with 'M' lozenge for easy distinction.

            James Dumay added a comment -

            Thanks Gergo

            James Dumay added a comment - Thanks Gergo

              Unassigned Unassigned
              f9b526421c43 Gergő Tisza
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: