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

Bamboo disables a plan if it was not published by RSS

XMLWordPrintable

    • 1
    • 5

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Bamboo disables a plan if it was not published by RSS

       

      Steps to Reproduce

      1. Create a Specs plan that handles and publishes two plans: PlanA and PlanB.
      2. Publish both plans (by doing a commit or scanning the repository from Bamboo).
        (no we have two new plans in Bamboo)
      3. Comment the publishing of PlanB. We want to force RSS to only publish PlanA.
      4. Run the Specs build again.

      Expected Results

      • PlanA will show the updated changes.

      Actual Results

      • PlanA will show the updated changes.
      • PlanB is disabled.

      No errors nor meaningful messages in logs.

      Workaround

      No workaround available

            [BAM-20740] Bamboo disables a plan if it was not published by RSS

            Vidas Drevinskas added a comment -

            Here is my use case and why i need not to disable plans:
            We store build configuration parameters in database. Currently there are 120 configuration, so 120 build plans. And we use one java bases bamboo-specs for converting all these configurations to build plans. So each time we change configuration for one plan, or add a new plan - all plans must be republished. This is annoying because:

            1. all plans get "Specs configuration updated" build and this leads to remove real build results for rarely used plans
            2. publishing so many plans take some time

            Vidas Drevinskas added a comment - Here is my use case and why i need not to disable plans: We store build configuration parameters in database. Currently there are 120 configuration, so 120 build plans. And we use one java bases bamboo-specs for converting all these configurations to build plans. So each time we change configuration for one plan, or add a new plan - all plans must be republished. This is annoying because: all plans get "Specs configuration updated" build and this leads to remove real build results for rarely used plans publishing so many plans take some time

            Vidas Drevinskas added a comment -

            I think current workflow could be left as is, it would be good to have workaround to avoid such behavior

            Vidas Drevinskas added a comment - I think current workflow could be left as is, it would be good to have workaround to avoid such behavior

            Pawel Skierczynski added a comment -

            It's a suggestion, because it would change the current workflow, that works as intended.

            We are open for discussion about potential use cases.

            Pawel Skierczynski added a comment - It's a suggestion, because it would change the current workflow, that works as intended. We are open for discussion about potential use cases.

              Unassigned Unassigned
              pdemitrio Patricio
              Votes:
              10 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: