- 10.1. Introduction
- 10.2. Installing the Nexus Staging Suite
- 10.3. Configuring Staging Profiles
- 10.4. Performing a Staged Deployment with Maven
- 10.5. Uploading a Staged Deployment in Nexus
- 10.6. Managing Staging Rulesets
- 10.7. Managing Staging Repositories in Nexus
- 10.8. Managing Staging Repositories with the Nexus Maven Plugin
If you release artifacts to users or customers, you will often need to test these releases before deploying them to externally accessible repositories. Nexus Staging Suite allows an organization to create a staging repository and to manage the promotion of artifacts from a staging repository to a release repository. Nexus Staging Suite provides an organization with a workflow for controlling releases.
Without the Staging Suite, when a developer deploys an artifact to a Hosted repository such as the Release repository, this artifact is published to a hosted repository and is immediately made available - there is no oversight, there is no approval or certification process. While this is acceptable for many Nexus users, organizations and enterprises with a QA cycle often need a temporary staging repository for potential release candidates: a staging repository. With the Nexus Staging Suite, an organization can automatically stage releases to temporary staging repositories which can then be used to test and certify a set of artifacts before they are published to a final release repository. The Staging Suite provides a mechanism for administrators to publish sets of artifacts that can be promoted or dropped depending on some release certification or testing procedure.
With the Staging Suite, when a developer deploys an artifact, Nexus will consult a set of Staging Profiles and automatically intercept the artifacts to be deployed. The Nexus Staging Suite intercepts the initial deployment using a Repository Target and creates a new temporary staging repository. The Staging Suite will then create a temporary, read-only staging repository and notify the appropriate Nexus users that a deployment has been staged. A staging administrator can then manage the availability of the staging repository and accept or reject the contents once they have been made available for testing. If the artifacts in the temporary staging repository are promoted, these artifacts are then published to the target repository.
