Jump to content
Serena Release Manager
After defining a component's source and processes, the artifacts are imported into the Release Automation asset repository. By default, a complete copy of an artifact's content is imported into the asset repository while the original artifacts remain untouched. This provides several benefits, such as tamper-proof storage and the ability to review and validate artifacts with Release Automation's user interface. But if you have storage concerns or use a tool like Maven, you can limit the asset repository to using references to the artifacts instead of actually copying them.
Each time a component is imported, it is versioned. Versions can be assigned automatically by Release Automation, applied manually, or come from a build server. Every time a component's artifacts are modified and reimported, a new version of the component is created. Therefore, a component might have several versions in the asset repository with each version being unique.
A version can be full or incremental. A full version contains all component artifacts; while an incremental version only contains artifacts modified since the previous version was created. The data tier also provides log file and the asset repository. Artifacts represent deployable items such as files, images, databases, configuration materials, or anything else associated with a software project. By default, these are stored in the asset repository's subdirectory in the Release Automation server installation directory.
Release Automation's secure and tamper-proof asset repository ensures that deployed components are identical to those tested in preproduction environments. Without the artifact repository, artifacts would have to be pulled from network shares or some other system, increasing both security risks and the potential for error. The artifact discovery uses content addressable storage to maximize efficiency while minimizing disk use. The repository tracks file versions and maintains a complete history for all components. Maximizing efficiency is important, since the artifact repository stores files that are much larger than source files. Association of files with components is built into the system. Without any configuration, each component gets its own area of the repository for its files. There is no chance of confusion or mix-up of files to components. And, each component package is mapped to a specific set of files and versions corresponding to the component.
The asset repository comes with a client application that provides remote access to the repository. Using the client, the user can add/modify files, create packages, retrieve files, as well as view the history of changes. The client application provides a file transfer capability that can be used to deliver files to target servers during deployments. This built-in transfer mechanism verifies the integrity of all transferred files against their expected cryptographic signatures, thus guaranteeing that files have not been corrupted during transmission or tampered with during storage. In addition to the client application, the vault exposes REST-based web services. These services are used to build integrations between build systems, such as AnthillPro, and Release Automation. Such integrations automatically place the artifacts produced by the build process in the artifact repository, thus making the artifacts available for deployment.