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

Run parameterized plan automatically from one plan without having to clone

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None

    • 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.

      I'd like to be able to run one plan but have multiple parameterized runs of that same plan. The key is here then I only have to modify one plan in one spot rather than cloning the existing plan and changing the parameters there. This is key for plans that have a high number of jobs. When you need to make changes to the tasks inside, if you had to clone your plan, then you need to edit multiple plans.

      So I could then run my CI trunk plan against JDK 6 and JDK 7, for example, without cloning.

      Certainly, allowing environment variables, capabilities and builders to be selected at the plan level would help this editing nightmare, but I think this is a great idea as part of the "run parameterized" concept.

      It's almost a plan within plans.

            [BAM-9382] Run parameterized plan automatically from one plan without having to clone

            Bryce Johnson [Atlassian] added a comment -

            Yep it's the same. Thanks Anton. I'll add a comment there.

            Bryce Johnson [Atlassian] added a comment - Yep it's the same. Thanks Anton. I'll add a comment there.

            AntonA added a comment -

            Guys,

            I think this is the same as BAM-9189. If it's close to it, could you add a comment to BAM-9189 to mention your usecase on it.

            If it's totally different, let me know and we will reopen this issue.

            Cheers,
            Anton

            AntonA added a comment - Guys, I think this is the same as BAM-9189 . If it's close to it, could you add a comment to BAM-9189 to mention your usecase on it. If it's totally different, let me know and we will reopen this issue. Cheers, Anton

            Matt Quail (Inactive) added a comment -

            This came out of a conversation between Bryce and myself: We have a fairly complicated plan with lots of jobs, and we want to paramaterize it in terms of the JDK it was using. But you can only invoke a Paramaterized Run manually. It would be nice if they could be scheduled, too.

            Matt Quail (Inactive) added a comment - This came out of a conversation between Bryce and myself: We have a fairly complicated plan with lots of jobs, and we want to paramaterize it in terms of the JDK it was using. But you can only invoke a Paramaterized Run manually. It would be nice if they could be scheduled, too.

              Unassigned Unassigned
              bjohnson Bryce Johnson [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: