Section | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Details
Options
File spec or folder name
Specify the file spec, or folder name to test.
Fileset
Specify the group of files/folders to check through the use of a FileSet.
Fail action if
File or folder is missing
Specify this option to check if the file/folder is missing. If the file/folder is missing, the action will fail.
File or folder exists
Specify this option to check if the file/folder exists. If the file/folder exists, the action will fail.
Do not fail
Specify this option to make the action no longer fail. This is useful when setting a variable with the result of the file/folder existence.
Set variable
Specify the variable to set with the result of whether the file exists or not. If the variable is not specified then testing for previous action failure is the only other way to perform action conditional on the files existence.
Examples
File must be present
- A critical file must be present:
- Specify the name of the file.
- On the Details tab, choose Fail Action If - File or Folder is Missing.
- Do not specify a variable.
The build will immediately abort if the required file is missing.
Warn user folder contains files
The user should be warned if any files are present in a directory.
...
The build will skip the sub-node if the file is not present, but will keep running.
Presences of file
Complex logic involving the presence of a file:
...