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

Make it possible for build trigger mechanism to ignore certain commits

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.

      Ignore criteria:

      • commit messages with a certain regex (predefined regexex for Maven commits)
      • commits done by a user on a configurable list
      • commits matching repository / branch (e.g. to ignore certain externals)
      • Whatever user wants via a plugin point for that.
        This should probably be available per repository, plan, project and globally.

            [BAM-10035] Make it possible for build trigger mechanism to ignore certain commits

            Ishwinder Kaur added a comment -
            Atlassian Update - 24 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.

            Kind regards,
            Bamboo Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 24 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Bamboo Data Center, please check our public roadmap . Kind regards, Bamboo Data Center

            lachland added a comment -

            Seems like the 'exclude changesets' feature cover this. If so, we should resolve this issue with a link to the documentation for this feature.

            lachland added a comment - Seems like the 'exclude changesets' feature cover this. If so, we should resolve this issue with a link to the documentation for this feature.

            Gregor Jasny added a comment -

            It would save us many useless Bamboo runs if we could ignore commits done by a certain user. Ignoring by file pattern does not work because these files are scattered across the source tree.

            Gregor Jasny added a comment - It would save us many useless Bamboo runs if we could ignore commits done by a certain user. Ignoring by file pattern does not work because these files are scattered across the source tree.

            Marco Wlotzka added a comment -

            I think, this feature is essential. Hudson and Team Foundation Server have both a solution for that.

            In Hudson: Polling can now ignore commits based on configurable keywords in the commit messages
            In TFS: http://stackoverflow.com/questions/3829305/what-does-no-ci-stand-for

            Possible solution: create a post-commit trigger which skips triggering when a keyword is found in the commit message. http://confluence.atlassian.com/display/BAMBOO/Repository+Triggers+the+Build+when+Changes+are+Committed

            Marco Wlotzka added a comment - I think, this feature is essential. Hudson and Team Foundation Server have both a solution for that. In Hudson: Polling can now ignore commits based on configurable keywords in the commit messages In TFS: http://stackoverflow.com/questions/3829305/what-does-no-ci-stand-for Possible solution: create a post-commit trigger which skips triggering when a keyword is found in the commit message. http://confluence.atlassian.com/display/BAMBOO/Repository+Triggers+the+Build+when+Changes+are+Committed

              Unassigned Unassigned
              pbruski Przemek Bruski
              Votes:
              10 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: