By the way you should use an IDE to write the groovy scripts (IDEA IntelliJ for example). I started with creating a separate repository for keeping my scripts and changes. So the easiest way to start is by cloning the repository and change it based on your own requirements. The above example project contains basic examples for different types of setup tasks to do. This can either been done using curl manually on command line or you can use the provision.sh script in example scripting setup which is much more convenient. First upload the script and afterwards run it.

There is a two step way to get something configured in Nexus. This can be started by using the following command:Īfterwards you can use the example scripts for provisioning as a starting point. You can simply get an default installation via a Docker Image. The simplest way to make experiments related to the Nexus Provisioning API is to use a Dockersetup. The Nexus Repository Manager starting with version 3+ provides a Provisioning REST API which allows to upload scripts to Nexus and execute those scripts which makes it possible to do such kind of setup in a scripted manner. If you are doing that more than once, it becomes cumbersome and you are asking yourself: Isn’t there a simpler solution to make that setup more reproducible?įortunately there is a solution for that problem. The problem with such setups is simple: You usually do it manually which in consequence is error-prone. Previously I was working on a Nexus Repository Manager setup for different environments like a test and a production environment with different privileges, roles, repositories, users etc.

Setup nexus repository