When the system runs a step, it can start from the directory it constructed for the job, or if the step's Path option is set to Absolute, it can ignore the project and tag directories.
Values for step |
Resulting path for command |
---|---|
Server's Path field: C:/BuildForge Step's Directory field: /bin Step's Path setting: Absolute |
C:\BuildForge\bin Use this form to access directories located in the server directory. |
Server's Path field: C:/BuildForge Step's Directory field: / (the default value) Step's Path setting: Absolute |
C:\BuildForge |
Server's Path field: C:/BuildForge Step's Directory field: C:/temp Step's Path setting: Absolute |
C:\BuildForge\C:\temp (This example will cause an error; the step will fail.) |
Values for step |
Resulting path for command |
---|---|
Server's Path field: C:/BuildForge Project name: My Project Tag: Job_5 Step's Directory field: /bin Step's Path setting: Relative |
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 Directory field do not exist, the step fails; the system does not create these directories. The portion of the path specified by the Step's Directory 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 the Path, either Relative or Absolute, and uses that as the default on new steps.