rh._.exports({"0":[[" ","Using Build Roles to Control User Builds"]],"1":[[" ","Using Build Roles to Control User Builds"," ","Optionally, Dimensions Build checks which build roles are required at each build stage, and verifies that the user running the build has the appropriate role. If user does not, the build request is rejected. This enables you to control which users can build at which stages."," ","The naming standard for build roles is as follows:"," ","Role names begin with BLD_ and end with the stage name."," ","Any blanks or spaces in the stage name are converted to an underscore (_)."," ","For example, the stage name SYSTEM TEST requires the role BLD_SYSTEM_TEST."," ","NOTE  ","The build roles are not mandatory, but if they exist they are required. Therefore, if the role for a stage is not defined, the build is allowed to progress. "," ","Disabling the Automatic Selection of Targets"," ","By default, targets are automatically selected by Dimensions Build. To disable this feature, specify the following variable in the Dimensions configuration file, dm.cfg:"," ","NO_BUILD_TARGET_PRESELECT PRODUCT1:PROJECT1, PRODUCT2:PROJECT2 …,"," ","Projects that you specify must be separated by a comma or a space. If a project specification contains commas or spaces, it has to be specified in double quotes."," ","For example:"," ","DM_NO_BUILD_TARGET_PRESELECT QLARIUS:PROJ1,QLARIUS:PROJ2 QLARIUS:PROJ3 \"QLARIUS:MY NEW PROJECT\", \"QLARIUS:PROJ A, WITH CHANGES\""]],"id":"254"})