What's the license needed for build engine?

Hi Feng,

the way this is supposed to work is as follows:

1. You can create up to 50 technical build accounts that represent build automation users that are used to run JBE's. These build users need to have access to the workspaces and streams they are supposed to build for. E.g. they need to be member of projects/teams to access streams and workspaces. Repository workspaces for private builds can't be private.
2. A regular user can trigger a build if the user has a developer license (needed for SCM operations).
3. When triggering a build, the responsible JBE grabs the build request and runs the build - using the build automation user license - on behalf of the requestor of the build.

here is my interpretation from the tip that appears when you hover your mouse over the license type in the License Key Management.  The tip gives us good information about the capabilities of each license kind.  Here is an extract of the same for Build System and Developer:

Client Access License Type : Build System
The Build System Client Access License is for assignment only to a user ID used by an automated Build System.  This enables the devices in the Build System to have read access to all capabilities, and write access to all capabilities unless otherwise restricted by role-based permissions.

Client Access License Type : Developer
Read and Write access to Change Management, Report Customization, Planning, Software Configuration Management, and Automation (Build System).

From this what appears to me is that you could assign either of these license to the user used for your automated builds.  However, by assigning Developer license to this user, the other capabilities that this license could be used for by a different user becomes unavailable.  So, it might be more appropriate to assign a Build System license which is specifically meant for this capability.

The "automated users only" restriction means that the terms of the license (that you agreed to when you downloaded the server) require that this license only be used by a fully automated process, and not by a human user.   So you can assign this license to a user account that is used by the Jazz Build Engine process to perform builds, but you cannot assign it to a human who uses it to perform interactive work.  A developer license can also be used by the fully automated process, but there is no charge for the Build System licenses, so you'd normally use those for the build accounts, and save your developer licenses for your human users.