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

Keep track of what/who triggered a build

XMLWordPrintable

    • 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.

      It would be nice to be able to see what / who triggered a build. This especially applies to dependency builds - to know which parent triggered the particular build.

      This was asked for as part of a request for better notifications i imagine it could be useful elsewhere.

            [BAM-1297] Keep track of what/who triggered a build

            edwin added a comment -

            Hi guys,

            This improvement is now officially released in Bamboo 2.0!

            For more information about the release, check out our release notes.

            You can download the latest release here today!

            Regards,
            Edwin

            edwin added a comment - Hi guys, This improvement is now officially released in Bamboo 2.0! For more information about the release, check out our release notes . You can download the latest release here today! Regards, Edwin

            MarkC added a comment -

            The reason for a build will now include who triggered off a manual build. e.g. "Manual build by Mark Chai" and which parent build kicked off a dependant build

            MarkC added a comment - The reason for a build will now include who triggered off a manual build. e.g. "Manual build by Mark Chai" and which parent build kicked off a dependant build

            Tatu Lahtela added a comment -

            So this means that currently I do not know who broke the build when it's caused by some change in a dependant build? E.g. someone makes changes to plan A - a component needed plan B -> Plan B tests fail because of the changes.

            Tatu Lahtela added a comment - So this means that currently I do not know who broke the build when it's caused by some change in a dependant build? E.g. someone makes changes to plan A - a component needed plan B -> Plan B tests fail because of the changes.

            AjayA added a comment -

            This could also be extended to keeping tabs on users who triggered manual builds (See, http://forums.atlassian.com/post!reply.jspa?messageID=257248224)

            AjayA added a comment - This could also be extended to keeping tabs on users who triggered manual builds (See, http://forums.atlassian.com/post!reply.jspa?messageID=257248224 )

              Unassigned Unassigned
              bmccoy bmccoy
              Votes:
              7 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: