External reviews
26 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Nexus Repository - Easy to configure repository for software artifacts
What do you like best about the product?
It allows us to store, organize, and retrieve artifacts like JAR files, Docker images, npm packages etc. We use its dependency management tools that enable us to define and track dependencies between artifacts, ensuring that the correct versions are used and resolving any conflicts.
What do you dislike about the product?
Getting started and configuring it requires a learning curve, especially for beginners or those unfamiliar with repository management systems. The flexibility and extensive configuration options of Nexus Repository can sometimes make it complex to set up and manage.
What problems is the product solving and how is that benefiting you?
Sonatype Nexus Repository solves the challenges of centralized artifact management, dependency control, and security vulnerabilities for our software development. Providing a single platform for storing and retrieving artifacts eliminates the need for scattered repositories and improves accessibility. The robust dependency management capabilities ensure the correct versions are used and resolve conflicts, enhancing software integrity and stability. As a proxy server, Nexus Repository optimizes the build process by caching frequently requested artifacts, resulting in faster build times. Integration with security tools enables automatic vulnerability scanning, helping users identify and address risks in their software supply chain. Fine-grained access control ensures that only authorized users have access to sensitive artifacts, protecting intellectual property and ensuring compliance. These benefits ultimately lead to increased productivity, improved software quality, and smoother collaboration among development teams
Review for Nexus Repository
What do you like best about the product?
Nexus has been very much useful for storing local snapshots for docker images, libraries and war files. This provides the feature of getting repositories from local or public repositories by configuration.
What do you dislike about the product?
Configuring nexus with Docker will have challenges in restoring the snapshots during critical failures. Also need to do whole configurations.
What problems is the product solving and how is that benefiting you?
Nexus is serving as a local repository to get libraries, snapshots and save docker images for the services and UI. Also we are storing node modules developed internally.
nexus as artifact repository manager
What do you like best about the product?
nexus is an artifact repository manager tool , used to store artifacts released in different environments,it let us save artifacts for both production and non production environment, it easily integrates with Jenkins using the plugin nexus artifact uploader and integrates easily with TeamCity and nolio
What do you dislike about the product?
as far as i used Nexus in building CI CD pipeline , i did not find any flaws in it , it was easily integrated with Nolio, Jenkins, TeamCity
What problems is the product solving and how is that benefiting you?
Nexus is artifacts repository , we can store different version of artifacts in it which can be distributed to different environment for deployment
Recommendations to others considering the product:
Nexus Repository Manager is recommended to store artifacts and maintain its version
Centralized management for 3rd party software
What do you like best about the product?
Unified access to all the team 3rd party software using centrelaized access , role based access managment is best feature
What do you dislike about the product?
nothing to mention i really appreciate the use of this software
What problems is the product solving and how is that benefiting you?
managing the third party software used by the team , storage for all binaries
Very likely to recommend Nexus Repo
What do you like best about the product?
I have used Nexus Repository Manager along side with Jenkins. The integration with Jenkins is very easy and having multiple versions of JARs in a project gets easier to manage with Nexus.
What do you dislike about the product?
There's nothing as such to dislike. I have come across an issue where in case of same version, JAR files gets replaced and there's nothing to get back the original one.
What problems is the product solving and how is that benefiting you?
Nexus Repository Manager is mostly used in case of Microservices project. Where you have multiple dependencies in a project with multiple versions. NRM handles this scenario very well. We can use the dependencies from Cloud itself.
A one-stop tool for all your component management woes
What do you like best about the product?
Nexus Repo Manager is an excellent tool for storing & distributing your binaries and artifacts across the globe among product teams located at multiple geographies.
The tagging & Staging feature of Nexus is bliss for a completely automated pipeline.
Fetching third-party dependencies in a secure environment is a great plus.
Support for a vast number of repository formats.
Also, the caching feature makes the builds faster & optimizes the build process.
If Nexus is hosted on AWS , then we can directly attach the repository storage to an S3 Bucket.
Its v easy to utilize Nexus IQ server along with Nexus Repo Manager, which is a great tool to examine threats in third party dependencies in code binaries.
The tagging & Staging feature of Nexus is bliss for a completely automated pipeline.
Fetching third-party dependencies in a secure environment is a great plus.
Support for a vast number of repository formats.
Also, the caching feature makes the builds faster & optimizes the build process.
If Nexus is hosted on AWS , then we can directly attach the repository storage to an S3 Bucket.
Its v easy to utilize Nexus IQ server along with Nexus Repo Manager, which is a great tool to examine threats in third party dependencies in code binaries.
What do you dislike about the product?
The database of Nexus Repo Manager is integrated along with the application.Its difficult to segregate the data from Orion DB if required.
The licensing of Nexus Repo Manager is based on the no. of users. This makes it tricky for the large organization to adopt it.
Sonatype Nexus documentation on Gradle is very limited.Should add more content to it.
The licensing of Nexus Repo Manager is based on the no. of users. This makes it tricky for the large organization to adopt it.
Sonatype Nexus documentation on Gradle is very limited.Should add more content to it.
What problems is the product solving and how is that benefiting you?
Nexus helps us in managing our build artifacts.
Multiple teams can access the artifacts from one centralized server without using any FTP or other file transfer systems.
Highly secure.
Tagging & Staging allows smooth move within a pipeline
We are also using Nexus IQ server which does the health checks of our repos/ artifacts regularly.
Our Build & release cycle time has reduced drastically after using Nexus.
Multiple teams can access the artifacts from one centralized server without using any FTP or other file transfer systems.
Highly secure.
Tagging & Staging allows smooth move within a pipeline
We are also using Nexus IQ server which does the health checks of our repos/ artifacts regularly.
Our Build & release cycle time has reduced drastically after using Nexus.
Recommendations to others considering the product:
Easy to Set-up
Prompt Support
Very Easy to understand & implement
Upgrades are simple
Great documentation
Prompt Support
Very Easy to understand & implement
Upgrades are simple
Great documentation
Efficient Repository Tool
What do you like best about the product?
Import possible of GIT Lab, filters possible.
What do you dislike about the product?
Lack of reporting Tool like Nexus Aiditor, audit imterface for librariea difficulr
What problems is the product solving and how is that benefiting you?
Components libraries, artifacta repository
Great tool. Easy to use and maintain
What do you like best about the product?
Simple tool that is easy to use. Wish some extra features and enhancements in the UI can be developed for better management.
What do you dislike about the product?
The documentation in https://help.sonatype.com/repomanager3 can be improved to be much more specific. Information on HA needs attention. Most of the questions related to HA are deflected by the customer support team to these documents that do not help.
What problems is the product solving and how is that benefiting you?
Storing binaries of different types of repo formats in an easy to consume manner.
Very powerful product for dependencies management
What do you like best about the product?
Easy to configure in order to setup dependencies directories from different sources : Maven, Python, .Net , ...
Many functionalities in order to control actions different users can realize on a specific repository for writing or reading access.
You can also use it as a proxy for your different packages managers : npm, python, .... so everything is downloaded to your Nexus repositories and cached for future consumers.
Many functionalities in order to control actions different users can realize on a specific repository for writing or reading access.
You can also use it as a proxy for your different packages managers : npm, python, .... so everything is downloaded to your Nexus repositories and cached for future consumers.
What do you dislike about the product?
Interface of version 3 is very limited. Repositories view has disappeared for regular users, and it would be great to be able to filter by repository in the "Browse Option"
What problems is the product solving and how is that benefiting you?
Nexus Sonatype helps us to manage the dependencies of our organization.
All software used is stored in our repositories, improving control, build repeatability , and reducing network traffic.
All software used is stored in our repositories, improving control, build repeatability , and reducing network traffic.
Recommendations to others considering the product:
Very good dependencies manager.
Professional edition seems to be quite expensive, but OSS edition is perfect for standard use.
Professional edition seems to be quite expensive, but OSS edition is perfect for standard use.
Nexus Repository from Sonatype OSS
What do you like best about the product?
Quite simple to have it working for maven artifacts.
What do you dislike about the product?
The interface is useful but it isn't pretty or confortable to use
What problems is the product solving and how is that benefiting you?
We storage the private maven artifacts of some of our projects, and control user that have access to those artifacts.
Recommendations to others considering the product:
Nexus is an good private maven artifact repository, with capacity to act as other SW repository (e.g. Docker Images) It is easy to set your components to be released in this private reposiotory.
As Maven Central repository runs also a Nexus Sonatype Repository, working with the Central repository or with self hosted Nexus OSS doesn't have many implications in the maven configuration of the artifacts, neither in the flow that artifact should follow whether publish public into Central or private into your own Nexus.
User management is quite good implemented allowing different access for each user regarding different level of access to each type of repository, but also inside the repositories can be configured regarding each of the artifacts, or groups of them.
User management hasn't integration with github or other Oauth2 providers, but you can make your own connector with the scrip executor that the Nexus provides.
Over all I believe is a good choice for maven/gradle artifact repositories, and I would give it a chance for other kind of SW.
As Maven Central repository runs also a Nexus Sonatype Repository, working with the Central repository or with self hosted Nexus OSS doesn't have many implications in the maven configuration of the artifacts, neither in the flow that artifact should follow whether publish public into Central or private into your own Nexus.
User management is quite good implemented allowing different access for each user regarding different level of access to each type of repository, but also inside the repositories can be configured regarding each of the artifacts, or groups of them.
User management hasn't integration with github or other Oauth2 providers, but you can make your own connector with the scrip executor that the Nexus provides.
Over all I believe is a good choice for maven/gradle artifact repositories, and I would give it a chance for other kind of SW.
showing 11 - 20