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

XMLWordPrintable

    • 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

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 7 April 2020

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

             

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 7 April 2020 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.   Thank you, Bamboo Team

            Charles Miller (Inactive) added a comment -

            One extension to this concept - notification when you're off the hook.

            • User carlfish checks code into SVN
            • His update triggers plans FOO and BAR
            • Bamboo calculates that this will trigger dependent builds BAZ and QUUX.
            • (optional) Bamboo adds together the estimated times for all these builds (taking into account those that might run in parallel) and notifies carlfish by IM: "You are now on the hook for plans FOO, BAR, BAZ and QUUX. Estimated time until you are free: 45 minutes"
            • If any of the identified builds fail, carlfish is notified
            • carlfish's Bamboo dashboard tells him which plans he is on the hook for, and his estimated time to freedom for each one.
            • (optional) If all builds are successful, carlfish is notified: "FOO, BAR, BAZ and QUUX successful. You are now off the hook"

            Charles Miller (Inactive) added a comment - One extension to this concept - notification when you're off the hook. User carlfish checks code into SVN His update triggers plans FOO and BAR Bamboo calculates that this will trigger dependent builds BAZ and QUUX. (optional) Bamboo adds together the estimated times for all these builds (taking into account those that might run in parallel) and notifies carlfish by IM: "You are now on the hook for plans FOO, BAR, BAZ and QUUX. Estimated time until you are free: 45 minutes" If any of the identified builds fail, carlfish is notified carlfish's Bamboo dashboard tells him which plans he is on the hook for, and his estimated time to freedom for each one. (optional) If all builds are successful, carlfish is notified: "FOO, BAR, BAZ and QUUX successful. You are now off the hook"

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

                Created:
                Updated:
                Resolved: