Files can be uploaded in bulk for use by Package Steps. This guide will explain some of the nuances involved when working with a large number of files or files of a considerable size.
Uploading Files or Folders
The File Copy Step, PowerShell Step, and the Install Step all have an Attachments button where you can choose to upload files or folders. The default selection will be Upload Files. To upload a folder, click the dropdown arrow and select Upload folder. Once the attachment type has been selected, click the Attachments button to open Windows Explorer and browse to the desired location.
Files may be uploaded individually or in bulk by highlighting multiple files at once. There is no practical limit to the number of files that may be selected simultaneously. Once all files have been selected, click "Open" in to begin uploading the files.
The selected files will be displayed in the Attachments box when uploaded.
In addition to the above, it's important to observe the following requirements when uploading files.
- A single file may not exceed 5 GB in size for uploads. This limitation is per-file and does not apply to the total size of all files combined. For example, you could not upload a single file that is 6 GB in size, but you could upload 2 files that are both 4 GB each, totaling 8 GB.
- Uploading folders during a bulk file upload is not supported. If you need to upload additional folders after attaching files, toggle the attachment button to Upload Folders and then select the folder you wish to upload.
- Uploading empty files such as a blank text file is not supported. Attempting to upload a 0 bytes file will result in an unsuccessful upload.
Uploading a folder will preserve the folder structure and include all files and subfolders contained in the original folder. This ensures that the underlying contents of the folder hierarchy may be correctly referenced by installers and scripts. The folder upload process has several nuances which should be taken into account.
- Unlike files, only one folder may be selected for upload at a time. Additional folders may be attached by repeating the folder upload process after the previous upload is complete.
- A single folder may only contain a maximum of 250 files. Files spread out across subfolders do count towards the 250 file limit of the top-level folder.
- Attempting to upload a folder that contains more than 250 files will result in a notification that the folder should be zipped. We will discuss working with zip files in greater detail below.
- There is no limit to the number of folders that can be uploaded in a single Package step, as long as no single folder includes more than 250 files.
- Uploading empty folders is not supported. If a folder contains an empty subfolder, that folder will need to be removed in order for the upload to succeed.
Working with zip files
When a zip file is included in an Install Step or PowerShell Step, the contents will automatically be extracted for use during the deployment. This works especially well with the Install Step, since you may be zipping files solely because the file count exceeds 250 files.
- Automatic unzipping of archive formats other than zip is not supported. This means that RAR files and 7z files will not be automatically extracted after they are copied to the machine.
- If you upload zip files that are nested inside another zip file, only the top-level archive will be unzipped. Automatic extraction of nested zip files is not supported.
- Zip files located in sub folders will be unzipped as long as they are not nested inside another zip file. If you upload a file that has 3 subfolders and each subfolder contains a zip file, all three zip files will be extracted in their respective folder.
- Zip files are classified as a file, not a folder. If you are compressing a folder because the total file count exceeds 250 files, "Upload file" should be selected as the attachment type.
- The File Copy Step does not automatically unzip files like the PowerShell and Install Steps. If you need to extract the contents of a zip file after copying it to a machine, we recommend using the Expand-Archive cmdlet in a PowerShell Step.