Artifacts are the physical files that make up a specific version of an application. For example, an application binary, configuration files, or web content. When adding an artifact to a deployment package, you can either:
This topic describes how to fetch artifacts from a Maven repository. You can access artifacts stored in a Maven repository using the fileUri property of Deploy artifacts. To use this feature, you must configure the Maven repositories that Deploy will search for artifacts.
When importing a package, Deploy scans the artifacts contained in the package for placeholders that need to be resolved during a deployment. You can turn off placeholder scanning using one of the following methods described in this topic.
Artifacts are the physical files that make up a specific version of an application. For example, an application binary, configuration files, or web content. When adding an artifact to a deployment package, you can either:
Deploy stores all of its information in the repository. The Explorer gives you access to the configuration items (CIs) in the repository and allows you to edit them manually.
You can configure Deploy to store and retrieve artifacts in two local storage repository formats:
To ensure that the downtime of your application is limited, Deploy can stage artifacts to target hosts before deploying the application. Staging is based on the artifact Checksum property, and requires that the plugin being used to deploy the artifact supports staging.
This topic provides some helpful tips and tricks to use when managing deployment packages.