Extract Files task
Azure Pipelines | Azure DevOps Server 2019 | TFS 2018 | TFS 2017
Use this task in a build or release pipeline to extract files from archives to a target folder using match patterns. A range of standard archive formats is supported, including .zip, .jar, .war, .ear, .tar, .7z, and more.
# Extract files # Extract a variety of archive and compression files such as .7z, .rar, .tar.gz, and .zip - task: ExtractFiles@1 inputs: #archiveFilePatterns: '*.zip' destinationFolder: #cleanDestinationFolder: true
|Archive file patterns||
The archives you want to extract. The default file path is relative from the root folder of the repo (same as if you had specified
Specify match pattern filters (one on each line) that you want to apply to identify the list of archives to extract. For example:
The pattern is used to match only archive file paths, not folder paths, and not archive contents to be extracted. So you should specify patterns such as
|Destination folder||Folder where the archives will be extracted. The default file path is relative to the root folder of the repo (same as if you had specified
|Clean destination folder before extracting||Select this check box to delete all existing files in the destination folder before beginning to extract archives.|
This task is open source on GitHub. Feedback and contributions are welcome.
Q & A
Where can I learn more about file matching patterns?
Q: I'm having problems. How can I troubleshoot them?
A: Try this:
On the variables tab, add
system.debugand set it to
true. Select to allow at queue time.
In the explorer tab, view your completed build and click the build step to view its output.
The control options arguments described above can also be useful when you're trying to isolate a problem.
Q: How do variables work? What variables are available for me to use in the arguments?
$(Agent.BuildDirectory) are just a few of the variables you can use.
Variables are available in expressions as well as scripts; see variables to learn more about how to use them.
There are some predefined build and release variables you can also rely on.
Do I need an agent?
You need at least one agent to run your build or release. Get an agent for Linux, macOS, or Windows.
I'm having problems. How can I troubleshoot them?
I can't select a default agent pool and I can't queue my build or release. How do I fix this?
See Agent pools.