The following example shows how the system uses several values to construct a job directory, in a job that occurs on a single server:
System Values |
Directory Created |
---|---|
Server's Path field: c:\BuildForge Project name: My Project Tag: Job 5 |
C:\BuildForge\My_Project\Job_5\ The system creates only the bold portions of the path. You must create the server directory before running the project, or it will fail. |
If a job occurs on more than one server, the system makes a job directory on each server. Since each step in a project can specify a different server, the system can potentially create many directories. The following example describes a project that uses two servers:
System Values |
Directories Created |
---|---|
Project server: ServerA, with Path value of c:\BuildForge Third step in project specifies ServerB, with Path value of c:\deployments. (All other steps use the default (project) server, ServerA). Project name: My Project Tag: Job_6 |
On ServerA: C:\BuildForge\My_Project\Job_6\ On ServerB: c:\deployments\My_Project\Job_6\ The system creates only the bold portion of the path. |
In the above example, you can expect any output files from a step to be created by default in the c:\BuildForge\My_Project\Job_6 directory, except for the third step, which uses the c:\deployments\My_Project\job_6 directory.