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

Do not run Change Detection after customized run

XMLWordPrintable

      Summary

      If a Trigger is enabled, Change Detection runs after a build and tries to trigger a new build with any changes (BAM-18497). With customized builds (Run >> Run Customized), users have the option to run off of custom commit hashes, which may be on different branches. In these cases, Bamboo will not be able to download the changes and run the build.

      Steps to Reproduce

      1. Add a branch more_tests to a build
      2. Configure a variable for the branch name (BRANCH_NAME)
      3. Add a trigger on the repository
      4. Do not merge more_tests to master
      5. Run a custom build using the more_tests branch

      Expected Results

      Build runs as expected

      Actual Results

      • A build ran as expected using the latest changeset on more_tests; but
      • Immediately after the build, change detection finds the delta between the revision used in the custom build and the latest revision on the master branch and triggers a new build

      The following appears in the Commits tab:

      [unknown]
Bamboo was unable to extract changes between revision <more_tests_commit_hash> and <master_commit_hash>.

      Workaround

      Remove any Triggers from the build

            [BAM-18527] Do not run Change Detection after customized run

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 2405074 ] New: JAC Bug Workflow v3 [ 3385968 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Scott Marshall added a comment -

            Better workaround: 

             

            1. Set your Change Detection Options to "only changes that match"
            2. Set the file pattern to .*

             

            That seems to stop the system from overwriting the custom build until an actual change occurs in the code repo

            Scott Marshall added a comment - Better workaround:    Set your Change Detection Options to "only changes that match" Set the file pattern to .*   That seems to stop the system from overwriting the custom build until an actual change occurs in the code repo
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Marcin Gardias made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Marcin Gardias added a comment - - edited

            Proposed change would break other customers' workflow and the desired functionality already exists in the form of Plan branches.

            Marcin Gardias added a comment - - edited Proposed change would break other customers' workflow and the desired functionality already exists in the form of Plan branches.

            Christian Monterroso added a comment -

            We are continuously seeing this issue. False failed builds are becoming costly as resources are spent investigating.

            Christian Monterroso added a comment - We are continuously seeing this issue. False failed builds are becoming costly as resources are spent investigating.
            SET Analytics Bot made changes -
            Support reference count New: 2
            Marcin Gardias made changes -
            Assignee Original: Marcin Gardias [ mgardias ]
            Krystian Brazulewicz made changes -
            Labels Original: bamboo-bugfix-kanban New: bamboo-bugfix-kanban-candidate

            Greg Niestrawski added a comment -

            Why make Bamboo's UX awkward when it could be slick? I understand where you're coming from, but a developer's life is difficult so the customer's life is easy

            "Customized Build" is more convenient as it is directly available to users from the Run > Run Customized menu item on the plan main page, and it does not require editing the plan or branch configurations. The workaround suggested above is more clicking, and requires more knowledge of Bamboo to understand.  I'm the Bamboo admin for my company, so I understand the suggested workaround (I just don't like it ).  I would have a hard time convincing the rest of our developers that the suggested workaround is the desired way to use the Bamboo build tool. I will also have a hard time justifying how the ghost build that I described in this ticket could be anything other than a design issue or bug that should be resolved.

            Greg Niestrawski added a comment - Why make Bamboo's UX awkward when it could be slick? I understand where you're coming from, but a developer's life is difficult so the customer's life is easy "Customized Build" is more convenient as it is directly available to users from the Run > Run Customized menu item on the plan main page, and it does not require editing the plan or branch configurations. The workaround suggested above is more clicking, and requires more knowledge of Bamboo to understand.  I'm the Bamboo admin for my company, so I understand the suggested workaround (I just don't like it ).  I would have a hard time convincing the rest of our developers that the suggested workaround is the desired way to use the Bamboo build tool. I will also have a hard time justifying how the ghost build that I described in this ticket could be anything other than a design issue or bug that should be resolved.

              Unassigned Unassigned
              ezeidan Ellie Z (they/them)
              Affected customers:
              3 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: