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

Commits made to repository while a build is running should trigger a subsequent build

    XMLWordPrintable

Details

    Description

      In Bamboo, we use "Stash repository triggers the build when changes are committed" triggers to start a plan. It works fine but except for one case - when a plan is already building and someone pushes code to Stash repo during that build, it won't be picked up by Bamboo and won't trigger new build when the current one finishes.
      Steps to reproduce:
      1. Create a Stash repo.
      2. Create Bamboo plan. Add the Stash repo (do not enable quite period) and add Stash trigger to the plan.
      3. Create a job that checks out the repo and a simple script task with "sleep 60" to make the build last about 60 seconds.
      4. Commit and push some changes to the repo.
      5. Observe how changes are picked up by bamboo, build is triggered automatically and runs for about 60 seconds.
      6. When build finishes start it again manually.
      7. Just after the build starts, commit and push new changes to the repo. This needs to be pushed while the manually-started build still runs.
      8. Observe how the changes are never picked up by bamboo and how new build is never triggered.

      Attachments

        Issue Links

          Activity

            People

              kbrazulewicz Krystian Brazulewicz
              rverschoor Rene Verschoor (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: