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

Bamboo YAML Specs plans are not getting automatically enabled after succesfull specs scan

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 9.6.0
    • 9.2.1, 9.2.10
    • Bamboo Specs
    • None

    Description

      Issue Summary

      Plans which are created by Bamboo YAML Specs gets disabled on Bamboo GUI when any incorrect changes are done on the specs file and the specs scan is done.

      When these incorrect changes are corrected and the specs scan in Bamboo in succesfull, the plan remains in disabled state, ideally it should get enabled automatically if the specs scan is succesfull.

      The only way to make this work in to enable all the plans manually and then do the specs scan, this creates problem when there are multiple plan under a single specs project

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. I've created two plans using Bamboo YAML Specs file, below is my specs structure from bamboo.yaml file

      ---
      !include plana.yaml
      ---
      !include planb.yaml
      

       
      2. In Bamboo two plans are created, all good till here.
       
      3. Now I do some changes in plana.yaml and those are incorrect changes and when I do specs scan it shows me some errors.Now both my Bamboo specs plans are disabled on Bamboo GUI, ideally it should have been just plana ( but okay still ).
       
      5. Now I fix my code in plana.yaml and try to import it under linked repository, the Specs scan shows as successful.

      Expected Results

      All the plans which got disabled should be enabled automatically as the incorrect specs code has been fixed and the specs scan is showing as Successful.

      Actual Results

      The Specs scan just shows as Successful and no action is taken on the disabled plans. The plans remains in disabled state and have to enable them manually one by one. 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

      Attachments

        Issue Links

          Activity

            People

              851f15845f55 Mateusz Szmal
              4f38d6bf51c0 Shashank Kumar
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: