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

Bamboo will loop into change detection when multiple Repository Commit tasks are used on the same plan

XMLWordPrintable

      Problem

      When a Plan has a "repository trigger" configuration and also has multiple "Repository Commit" tasks, Bamboo will loop endlessly as it will only ignore one of the "Repository Commit tasks" and will consider the other commits as trigger candidates.

      Environment

      Bamboo 8, possibly 7

      Steps to Reproduce

      1. Create a Linked Repository
      2. Create a Plan linked to that repository
      3. Make sure to add a Repository trigger
      4. Create a Checkout task, a "build task" that will change files
      5. Add a "Repository Commit" task
      6. Add a second "Build task", change more files (git add them if needed)
      7. Add another "Repository commit" task
      8. Run the Plan manual or via a commit trigger
      9. Watch the endless loop

      Expected Results

      Bamboo should run the Plan once and ignore any triggers whose origin are related to the "Repository commit" task

      Actual Results

      The build runs endlessly in a loop. Need to stop it manually.

      Workaround

      Standardise a "Commit message" in your build Plan scripts and Commit tasks and add a regular expression to the Linked Repository's Change detection options -> Exclude changesets, that will be used to ignore any commits coming from Bamboo. E.g.:

      ^\[BAMBOO\].*

      The above regular expression will ignore any commit message that starts with [BAMBOO] and will not trigger any additional builds.

          Form Name

            [BAM-21613] Bamboo will loop into change detection when multiple Repository Commit tasks are used on the same plan

            Sylwester Jeruzal (Inactive) added a comment - - edited

            We are aware of the limitation and we have some solution for it already (Workaround).
            To prevent the loop from triggering, you can define regular expression to match the commit messages to be excluded (in repository configuration).

            Sylwester Jeruzal (Inactive) added a comment - - edited We are aware of the limitation and we have some solution for it already (Workaround). To prevent the loop from triggering, you can define regular expression to match the commit messages to be excluded (in repository configuration).

              Unassigned Unassigned
              73868399605e Eduardo Alvarenga
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: