Importing Your Asset Zip File
Topic:
Assets
One you have created an asset zip file according to this article, you will want to import it into Arcus. To do so:
- On the main menu, next to Applications, click the Add button
Note: if you do not see the Add button, you need asset developer permissions in your project. Contact your Team Manager or Project Owner to set your project permissions.
- If you have an asset zip file to import, click on the “I have an archive with a properties file” option, click “Next”
- Drag and drop, or browse and select your asset zip file
- You will see a file transfer bar at the bottom right
- Keep an eye out for error notifications at the bottom left, in case any asset structure issues were detected
- You should receive an email notification if your asset import succeeded, if it fails the notification will provide details:
- If Arcus finds a problem with the asset
- If Arcus detects a virus or malware in the asset. If you feel this is in error, please enter a support ticket via support@arcus-cloud.io
- If you are having trouble importing your asset, see the section below for some typical troubleshooting steps
Troubleshooting Asset Imports
If you imported your asset but did not receive an email notification with a specific error message, please check these items and re-try your import:
- Ensure your asset zip file was zipped at the contents level, and the parent directory was not included in your asset zip file
- Ensure that the asset structure is correct as described here
- Ensure the install, checkout, build, and deploy scripts, and documentation files are each individually less than 4 MB
- If you are importing an asset larger than 4 GB, enter a support ticket
- Ensure the
asset.properties
file is at the top level of the zip file - Ensure your asset zip did not include the parent folder (just the contents of the folder)
- Is the “scripts” directory missing?
- Are there media files outside of the media directory?
- Are the license and readme files at the location specified in the asset.properties file?
- Does the
installScript
file name in asset.properties match the files in the “scripts” directory? - If license and readme files are included at the root, ensure the
documentationFile
andlicenseFile
properties have the correct file names - Ensure there are no files at the root of the asset except the
asset.properties
, license, and documentation files
More Help
Review this process with our video tutorials: