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

Child plan is triggered independently of Parent's build result

    XMLWordPrintable

Details

    Description

      Stash v3.6.0
      Bamboo v5.7.2

      Replicate issue (Only trigger "Plan C" if "Plan A" and "Plan B" builds are successful)
      1. create a repository in Stash
        • add the following content to the repository
          ./planA
          ./planB
          
      2. create a Project in Bamboo
        • create a Plan (Plan A)
          • set up Stash repository under "Plan configuration >> Repositories" tab
          • under "Advanced options", please select "Include only changes that matches" under "Include / Exclude files"
          • add the following to "File pattern"
            ^planA/.*
            
          • under "Plan configuration >> Triggers" tab, please select "Stash repository triggers the build when changes are committed" as "Trigger type"
          • under "Plan configuration >> Dependencies" tab, please add "Plan C" under "Child plans"
          • add "Source Code Checkout" task
        • run build
        • create a Plan (Plan B)
          • set up Stash repository under "Plan configuration >> Repositories" tab
          • under "Advanced options", please select "Include only changes that matches" under "Include / Exclude files"
          • add the following to "File pattern"
            ^planB/.*
            
          • under "Plan configuration >> Triggers" tab, please select "Stash repository triggers the build when changes are committed" as "Trigger type"
          • under "Plan configuration >> Dependencies" tab, please add "Plan C" under "Child plans"
          • add "Source Code Checkout" task
        • run build
        • create a Plan (Plan C)
          • add Script task
            echo "hello world!"
            
        • run build

      At this stage, you should have successful builds in "Plan A", "Plan B" and "Plan C".

      Lets force a build failure by:

      1. going to "Plan A >> Plan configuration" and add an "Ant" task
      2. please, run build

      At this stage, you should have successful builds in "Plan B" and "Plan C" but not "Plan A"

      Lets commit something to "./planB" directory as this will trigger "Plan B".
      Based on the configurartion above, "Plan C" will be triggered eventhough "Plan A" has a failure build.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rsperafico Rafael Sperafico (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: