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

Users who commit to any failing build are "on the hook" until success

    • 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Charles mentioned a build server that he used a long time ago (Continuum?) had a neat feature where the original committer who caused a build failure would be "on the hook" until the build passed. In addition, anyone who committed to a failing build and didn't make it pass (and therefore could have broken more stuff) would also be "on the hook" until the build passed. Once the build passes, everyone that is on the hook gets "let off the hook".

      This notion seems useful, particularly for notifications. It would be great if IM notifications only went to people on the hook. The current notification scheme only allows committer notifications, which isn't as useful when there are multiple commits while the build is failing.

      It would be also good to have a telemetry screen with mug-shots of those users who are "on the hook". This gives the team an idea of who is (or should be) fixing the build at the moment.

      This could possibly be developed as a plugin; I'm not sure how customisable these things are in Bamboo. It's probably a matter of adding some new metadata to a failing build (a list of users who are on the hook), and exposing that for use by notification schemes.

      If it can't be a plugin, I think it would be a useful addition to Bamboo core.

            [BAM-1339] Users who commit to any failing build are "on the hook" until success

            No work has yet been logged on this issue.

              Unassigned Unassigned
              matt@atlassian.com Matt Ryall
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: