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

Code changes detected during Quiet Period not appearing in Code Changes list and consequently triggered a new build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • None
    • 2.1.5
    • Triggers
    • None

    • Atlassian Bamboo version 2.1.5 build 1009 - 02 Dec 08
      Subversion SVN Repository

      When bamboo detected a change (CHANGE-A) for a build plan from Subversion, it has the "Quiet Period" capability to wait for more changes in order to build for a batch of changes. However, from our observation, we found the changes (CHANGE-B and CHANGE-C) detected during the quiet period is not made into the "Code Change" list after the build (BUILD-1) is finished successfully. The list only contain the change (CHANGE-A) that "triggered" the build.

      Even worse, the changes (CHANGE-B) and (CHANGE-C) triggered a new build (BUILD-2), which is an unexpected trigger since (CHANGE-B) and (CHANGE-C) were already included in (BUILD-1). This behavior produce incredible result since it triggers a chain of dependency builds, thus occupying the build agent, which should spend the time processing other build plans.

      I can reproduce this problem consistently in Bamboo 2.1.5 using Subversion repository.

      I also attached the screenshot of the Source Repository configuration which includes the Quiet Period settings.

      Please kindly advise if there 's anything configured improperly.

      Also, what happens for the code changes detected during queue time before the build start checking out code for "Force Clean Build". Would the changes be included in the "Code Change" list?

      Thanks.

        1. BambooBuildConfig.jpg
          95 kB
          Henry Chan

            [BAM-3904] Code changes detected during Quiet Period not appearing in Code Changes list and consequently triggered a new build

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1434690 ] New: JAC Bug Workflow v3 [ 3379307 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1408797 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1434690 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 609552 ] New: Bamboo Workflow 2016 v1 [ 1408797 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 602324 ] New: Bamboo Workflow 2014 v2 [ 609552 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 204864 ] New: Bamboo Workflow 2014 [ 602324 ]
            MarkC made changes -
            Workflow Original: reviewflow [ 174635 ] New: Bamboo Workflow 2010 [ 204864 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ulrich Kuhnhardt [Atlassian] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Ulrich Kuhnhardt [Atlassian] made changes -
            Assignee New: Ulrich Kuhnhardt [Atlassian] [ ukuhnhardt ]
            Henry Chan made changes -
            Attachment New: BambooBuildConfig.jpg [ 31611 ]
            Henry Chan created issue -

              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              0682f66549fc Henry Chan
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: