Skip to content

Filesystem actions ​

Filesystem actions operate on paths visible to the machine running the pipeline. They need no account credentials. A path outside the host's readable or writable areas can fail because of normal filesystem permissions.

ActionInputs and defaultsOutput
Zip (legacy)Required folder and output pathspath, the archive path
Zip (v2)Required folder; writes output.zip in the task cache by defaultpath, the archive path
Unzip fileRequired file; extracts into the task working directoryoutput, the extraction directory
Copy file/folderRequired from, to; recursive, overwrite, and cleanup default to trueoutput, input, parentDirectory paths
Remove file/folderRequired from; recursive defaults to trueNone
Run CommandRequired command; parameters defaults to []; optional workingDirectory defaults to the process current directory; stopOnError defaults to falsestdout, stderr, exitCode, duration
Open path in explorerRequired pathmessage

The v2 Zip action has no visible outputPath field, although its runner accepts one internally; in the task editor, expect the cache output.zip default. Unzip's output is the working directory, not a directory chooser. Run Command executes the named program with the listed arguments; it does not evaluate a shell command string. If stopOnError is enabled, a nonzero exit causes the task to fail. Opening a path depends on the host OS desktop handler, so it may not work in headless execution.

Minimal example: run a command ​

text
command: node
parameters: ["--version"]
workingDirectory: <leave empty>
stopOnError: true

The process output and exit code are available as task outputs. The duration output is currently set to 0 by the runner. An unavailable executable or process launch error fails the task. The former Invoke File label is not the registered action name; use Run Command. List files is not currently registered.

Released under the MIT License.