-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
2.1.5
-
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.
Dear Henry,
I have moved your issue to our jira support instance to ensure a more timely and prompt solution of your issue.
https://support.atlassian.com/browse/BSP-1824
Should you have more support related issues please use http://support.atlassian.com
Thanks for your understanding.
Ulrich Kuhnhardt,
Atlassian Support