Uploaded image for project: 'Bamboo'
  1. Bamboo
  2. BAM-12846

Per-branch-plan capability requirements

    XMLWordPrintable

    Details

    • UIS:
      1
    • Support reference count:
      3
    • Feedback Policy:

      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.

      Description

      Possibly covered by, or at least related to BAM-12232, we've begun to encounter situations in which branch plans may differ in their capability requirements: specifically, the situation I'm thinking of is where a release branch has been built using, say, JDK 1.6, but we're moving the techstack from 1.6 to 1.7; in this case, we might want to move most of the agents to the 1.7 capability, but keep an agent that only advertises 1.6 capabilities to ensure that hotfixes can continue to be built until we're fully able to confirm the ability of an agent to switch between 1.6 and 1.7.

      This would apply to testing that requires specific environments, etc. The ability to specify a per-branch-plan capability requirement would require more setup on our end, but would guarantee the stability of branch builds in specific environments without having to promote a branch-plan to the top level to specify its available agents.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              4c7f42da203a John Knight
              Votes:
              29 Vote for this issue
              Watchers:
              20 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: