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

All plan branches are set to master (default branch) if the repository configuration is re-added

XMLWordPrintable

      Steps to Reproduce

      1. Create a Plan in Bamboo with a Bitbucket linked repository
      2. Create multiple plan branches pointing to branches in the same repository
      3. Remove the Bitbucket linked repository from the tested plan
      4. Add the linked repository back to the plan

      The same behavior is observed if the repository order is changed inside the plan.

      Expected Results

      The source branch of the plan branch is pointing to the branch is was designated when created

      Actual Results

      Once the repository is removed/added all the plan branches are set to the default source branch configured in the linked repository.

      As s symptom, every change in the default branch will trigger the build for all the plan branches

      Workaround

      Manually set back the right branch on each of the plan branches of the affected plan.
       Try to avoid removing or changing the order of the repositories.

            [BAM-20061] All plan branches are set to master (default branch) if the repository configuration is re-added

            vergiliu added a comment -

            The repository type (linked or not) seems to have no influence, still only master is being checked out

            vergiliu added a comment - The repository type (linked or not) seems to have no influence, still only master is being checked out

            vergiliu added a comment -

            On 6.6.0 the same behavior seems to be present - this is a major issue especially when many plans are affected at once - making the Specs rather useless from the perspective of the plan's branch configuration

            vergiliu added a comment - On 6.6.0 the same behavior seems to be present - this is a major issue especially when many plans are affected at once - making the Specs rather useless from the perspective of the plan's branch configuration

            Chas Berndt added a comment -

            We're seeing this issue in 6.5.1 and we'd love to have this fixed in 6.5 as this bit us big time on a linked repo with several hundred branch plans. Currently, the only way to fix it is to manually go through branch plans and update them to the correct branch.

            Chas Berndt added a comment - We're seeing this issue in 6.5.1 and we'd love to have this fixed in 6.5 as this bit us big time on a linked repo with several hundred branch plans. Currently, the only way to fix it is to manually go through branch plans and update them to the correct branch.

              mgardias Marcin Gardias
              dsantos Daniel Santos (Inactive)
              Affected customers:
              13 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: