Project vs Build Configuration in Professional Edition
Hi,Im trying to understand the impact of the 20 configuration restriction in the Professional edition. Does this effectively mean that I cannot have more than 20 projects?
Please sign in to leave a comment.
This is a restriction for 20 build configuration in total, no matter how they are split between projects.
Yes, but then, can I share build configurations between projects? The documentation does not make the project/configuration relationship very clear...my bottom-line question is: am I limited to a number of projects or not?
Projects are like containers for build configurations - they allow to group related configurations together, and allow to set common properties or permissions.
Right, so if I have 5 projects, each with 4 configurations, I have maxed out my installation.
Some clarification -
in pulse: 1 project group with 2 projects
First project have several build specifications: cluster, read_only test, hard_test, load ground stress, default.
Second project build specifications: default.
This mean that we use 6 build configurations (build specifications count) or 1 (project groups count) or 2 (project count) ?
Thanks in advance
6 build configurations.
You can find the counter at Administration page: