The nexus role is used to setup the artifact management software, while the client role sets up the pip settings on every machine.

There are two roles: ‘nexus’ and ‘clients’.

I divided the tasks in groups and the resulting playbook looks like this: Nexus3OnOrangePI]$ tree -N ansible/ Installation instructions for Ansible are easy to follow.

Ansible controller will run on the Fedora machine, but any server can be the controller.

My cluster has a mix of Raspberry PI 4 and an OrangePI 5.

Two or more Linux machines (I used Debian, Armbian and Fedora IOT), with at least 8 GB of RAM.

An Internet connection to download the source code for the Ansible playbook, Nexus, and PIP modules.

What you need to run the code from this tutorial Part of the setup will consist of setting a proxy for, for the machines listed on my inventory file. Nexus 3 will run on an Orange PI 5 computer with 8 GB or RAM, but this provisioning can be done on any machine with the minimum requirements. In this article I will show you how you can download, install, and configure the OSS version of Nexus 3 using an Ansible playbook.

Segregate who can have access to your artifacts: You may have more strict requirements on who can access some artifacts within your own organization.

Control what artifacts make it to your build chain: Centralize the location of the artifacts, ensure they are approved for usage, and also confirm than they do not contain malicious code.

Faster artifact download speeds: If you constantly download the same artifacts over the Internet, you can cache them on a central location, for the benefit of your multiple users across multiple servers by caching them.

Use your private infrastructure: You may have proprietary code that needs to be safeguarded.

Why have an on-premise artifact manager? There are many reasons for it: Nexus 3 OSS is an Open Source artifact repository manager that can handle multiple formats like container images, Python PIP, Java jar, and many others.

Download sonatype nexus 3