Artifact management lets your organization deploy an application with build files and other types of software artifacts without regard to their physical location.
An artifact is a script or the output of a build process. With artifact management, an application blueprint specifies an artifact by type and name, but not by location or unique identifier. Artifact management monitors the physical location and identity of artifacts and supplies the required artifact during deployment.
In artifact management, an application catalog administrator creates artifact repository specifications and maps them to artifact repository instances. An artifact repository specification identifies a store that can contain an unlimited number of artifacts. It has properties that identify an artifact repository instance and the artifacts it contains. Application Services provides out-of-the-box artifact repository specifications for Jenkins and YUM, and the capacity to define additional artifact repository specifications.
An application architect and other application administrators create artifact specifications, map them to artifact repository instances such as actual Jenkins build projects, and then bind the artifact specifications to the properties of services, external service, or application components such as WAR or JAR files in the application blueprints. An artifact specification identifies an artifact only by name, description, and business group. The deployment environment you select determines the actual artifact repository instance, and the deployment profile you use specifies the actual artifact. You can map an artifact to one repository instance per deployment environment.