Some organizations may want to lock down the components that a release build can depend upon. It is also a good idea to make sure that your build isn’t going to be affected by changes to a repository not under you control. A procurement administrator can configure a procured repository, start procurement, and run an enterprise build against the repository to populate the procured, hosted repository with all of the necessary components. After this process, the procurement administrator can stop procurement and continue to run the same release build against the hosted repository that now contains all of the procured components while being a completely static repository.
To stop procurement, go to the procurement management interface by clicking on Artifact Procurement under the Enterprise section of the Nexus menu. Right-click on the repository and choose Stop Procurement as shown in Figure 10.17, “Stopping Procurement for a Procured Repository”.
After choosing Stop Procurement, you will then see a dialog confirming your decision to stop procurement. Once procurement is stopped, the procured repository will revert back to being a hosted repository.
In order to add further components, you create a procurement repository off the hosted repository as you did initially. If the repository contains components already, activating procurement will automatically generate rules that allow all components already within the repository.