Using Build Forge variables to choose a step path at run time
Include a variable for the directory in which you want the Build Forge step to execute in your environment. Use a default value, or make it a “must change” variable. Place the variable in the step path, i.e. $var_name. Using drop-down variables to limit users to a pre-selected choice of paths is another option.
Using Build Forge variables to choose selectors or servers at run time .
Include variables for the Build Forge servers and/or selectors in your environment. Using drop-down variable is generally the best choice, as no one, including yourself is likely to remember the names of available servers and selectors. Use the .bset dot command to assign different servers and/or selectors for different steps.
.bset server $server_variable
.bset selector $selector_variable
Create classes that can’t be created by the GUI
Using Build Forge’s GUI, create a retention class. Then, update the Build Forge data base to any arbitrary count or days for that class. See a more complete explanation here.
Block execution of selected projects for users that have overall execution permissions without blocking visibility.
To prevent users from executing specific projects, while still maintaining their ability to see the projects and jobs and to evaluate execution results, choose a Build Forge selector, environment, or servers to which they do not have access. Continue to allow access to all other parts of the project. You can see a fuller explanation of how to accomplish this here. A deeper discussion of using Build Forge groups can be found here.