Constructing directory paths for steps

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.

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.


Feedback