BuildForge Help

Changing Project Properties

To change project-level properties, select Projects, then click the Figure shows edit (pencil) icon icon next to the desired project's name.

Project Name
The name of the project; used to refer to the project in lists and in the database.

The project name is used to construct the project directory when the project is executed. The system allows you to use any characters you like in the project name; it's up to you to make sure the project name does not contain characters that are invalid. Since a project may contain steps that run on different operating systems, avoid special characters and symbols in your project names.

Access
The access group allowed to view and use the project. The Access property is used along with permissions to determine what a user can do. For example, to launch a job, you must be a member of the access group specified for the project, and you must also be a member of a group that has the Execute Jobs permission. See Security Overview for more information.
Tag Format
A string that defines the tags for the project, using plain text and tag variable references. See Tagging Jobs Dynamically for more information on tag formats.
Tag Sync
Synchronize the tag variables for two projects. Select the project whose tag variable you want to synchronize with the current project. When two projects are synchronized, their variables are drawn from the same pool, so that when they run in sequence, one project gets the value 1, the next gets the value 2, and so on. See Synchronizing Tags.
Max Threads
The maximum number of parallel processes the project is allowed to launch. Use this field to keep a project from using too many system resources. Each thread-enabled step and any inline projects (which themselves might launch thread-enabled steps) can result in parallel processes, but all of those processes are counted against the maximum for the parent project. The system stops launching new parallel processes when it reaches the Max Threads value, and waits until the number of parallel processes for the project drops below the Max Threads value before continuing. See Threading: Running Steps in Parallel for more information on threading.
Run Limit
The Run Limit property sets the maximum number of jobs of the project that are allowed at one time. If you launch a project, but the currently active jobs already equal the limit, the new job stays in the Waiting queue until one or more of the jobs completes. If a schedule attempts to launch a project when the number of running projects equals the run limit, the system does not launch a new job at all. Also, projects that are launched via an inline chain are not considered instances of the original project and do not count towards its run limit.
Class
Each project must be assigned to a class, which assigns global properties to groups of projects. See About Classes for more information.
Selector
The name of the selector to use when choosing a server for the project. The system uses this selector as the default for any steps within the project that do not specify their own selectors. See Selectors. If a selector is not specified, the project is added to the Libraries module instead of the Projects module. Library projects use the selector of the calling project.
Pass/Fail Chain
Select the project that is executed when the project build passes or fails. Setting a pass/fail chain at the project level allows you to invoke separate pass/fail actions based on the pass/fail status of the project. This capability is similar to setting pass/fail actions at the step level within a project. At the project-level, the pass/fail actions are triggered by the project run status not the step status.
Environment
An environment to apply after the Server environment and before the Step environment. For more information on how environments work together, see How the System Applies Environments to Steps.
Sticky
Enable the Sticky check box to force all the steps of the project that use the default project server to stay on the same server, and to wait for it to become available if it is busy. For more information on this option, see Making Steps Stick with a Server.
Start Notify, Pass Notify, Fail Notify
Use these fields to direct the system to send notification e-mails on project start, pass, and/or fail, by selecting an access group in one or all of these fields.
Related concepts
Setting Notification Properties of Projects and Steps