Staging Profiles define the rules by which artifact deployments are staged in Staging Repositories. Staging Repositories are created as they are needed and are the primary mechanism by which Nexus users can promote or discard the contents of a staging repository to a hosted repository. A staging profile uses a Repository Target to match artifacts as they are deployed. If a matching artifact is deployed to Nexus, the Staging Suite will intercept this deployment and store the artifact in a staging repository.
The process for configuring a new Staging Profile is as follows:
- Configure a Repository Target to match artifacts under the groupId you will be deploying artifacts to. If you are releasing all of your software under the groupId com.example, you would configure a target that matches the pattern "./com/example/.".
- Create a new Staging Profile using the target defined in the previous step. When you configure this staging profile, you will be defining a target repository group. When the Staging Suite intercepts an artifact and places it in a staging repository, this staging repository will be added to the specified target repository group.
- Assign the appropriate Staging-specific roles to the appropriate users. When you create a Staging Profile, Nexus also creates two new roles that grant access and privileges to the repositories created by this Staging Profile.
The following sections provide a more detailed look at the process of configuring a single staging profile in Nexus Professional.
