When the system executes a step, it can start from the directory it constructed for the job, or it can use the Absolute option to ignore the project and tag directories.
When the Absolute box is checked, the system constructs the path for the step by adding together the server path and the step's Dir field. The value in the Dir field is a path relative to the server's working directory.
Values for Step |
Resulting Path for Command |
---|---|
Server's Path field: c:/BuildForge Step's Dir field: /bin Absolute check box: Checked |
C:\BuildForge\bin Use this form to access directories located in the server directory. |
Server's Path field: c:/BuildForge Step's Dir field: / (the default value) Absolute check box: Checked |
c:\BuildForge |
Server's Path field: c:/BuildForge Step's Dir field: c:/temp Absolute check box: Checked |
c:\BuildForge\c:\temp (This example will cause an error; the step will fail.) |
When the Absolute box is not checked, the system constructs the path for the step by adding together the server path, the project name, the tag, and the step's Dir field. The value in the Dir field becomes the path relative to the job's working directory.
Values for Step |
Resulting Path for Command |
---|---|
Server's Path field: c:/BuildForge Project name: My Project Tag: Job_5 Step's Dir field: /bin Absolute check box: Not checked |
C:\BuildForge\My_Project\Job_5\bin Bold portions of the path are constructed by the system if they do not already exist. Note: When it creates a project
directory, the system changes characters specified in the Invalid
Relative Dir Characters system setting into underscore characters.
By default, the setting contains a space and a backtick character, so that
a project named "My Project" receives a project directory named "My_Project".
|
If the directories specified in a Server's Path field or a Step's Dir field do not exist, the step fails; the system does not create these directories. The portion of the path specified by the Step's Dir field must be explicitly created during the project by a preceding step.
Typically, steps early in a project check out a tree of directories from source code control, and following steps act on those directories.
When you add new steps, the system remembers the last setting you chose for this check box, and uses that as the default on new steps.