Apache Archiva vs. Jenkins

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Archiva
Score 8.0 out of 10
N/A
Apache Archiva is a software repository management solution.N/A
Jenkins
Score 8.3 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A
Pricing
Apache ArchivaJenkins
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache ArchivaJenkins
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache ArchivaJenkins
Considered Both Products
Apache Archiva
Chose Apache Archiva
  • Apache Archiva is a great choice for organizations with a limited budget.
  • Alternatives are expensive to acquire Archiva comes offers REST API(s) which allows the creation of customized UI.
  • With Apache Archiva, it is easy to manage the remote proxy repositories.
Jenkins
Chose Jenkins
Jenkins is highly customizable, making it ideal for complex pipelines that require scripting, conditional logic, and integration with a variety of tools.Jenkins offers thousands of plugins, giving it unmatched versatility.
Chose Jenkins
Jenkins is highly customizable and flexible, supporting a wide range of plugins and integrations. Jenkins works with any version control system (Git, Subversion, etc.). Jenkins has a more mature ecosystem, and it may be better for large-scale, complex environments, especially …
Chose Jenkins
One of the most important factors for selecting Jenkins would be the cost. Since Jenkins is opensource, there is a good amount saved from licensing and software procurement costs. Apart from cost, Jenkins is easy to understand and there is wide range of documentation and …
Chose Jenkins
Bitbucket building was very slow, in order to improve that you have to upgrade to spend double or more minutes per build minute. The GUI was also very slow in updating on the progress of the builds, making things rather confusing. Gitlab worked a bit better in my opinion, but …
Chose Jenkins
Jenkins is very easy to use, open source tool. Its better for simple build and deployments.
Chose Jenkins
GitLab CI and Github Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform.
But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
Chose Jenkins
I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
Chose Jenkins
Didn't really check other tools in detail since Jenkins served all our requirements and has been hugely popular.
Chose Jenkins
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used …
Chose Jenkins
Honestly, we use Jenkins for pretty much everything exclusively, so it's hard to compare.
Chose Jenkins
It's mostly stable and well-known within the DevOps community.
Chose Jenkins
We have not evaluated other similar products.
Chose Jenkins
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Chose Jenkins
Jenkins is the only solution that we've tried that just automatically generates builds.
Chose Jenkins
Jenkins is easy to set up and supports a wide range of plugins. So any type of deployment is very easy. We can easily deploy Node, Angular, React, Java, Python, etc. Projects. We can also provide different credentials to different employees. So easy to track what is done by …
Chose Jenkins
Team services, while very similar, did not really have that much more added features for the much higher price tag. The team has moved over to the subscription-based Visual Studio so we may be reevaluating this solution as now it is part of our subscription and no longer an …
Chose Jenkins
I don't have any experience with alternatives to Jenkins.
Chose Jenkins
Originally Jenkins was selected because it was the best around, but it has since been outclassed by more specific services or cloud-based services and tools that will do all of the heavy lifting for you. Jenkins still has a use case - but it's hard to argue the additional …
Chose Jenkins
The big difference between Jenkins and other alternative tools is that Jenkins is open source and it’s free. Jenkins is very much about simple functionality. It’s a general CI tool that offers basic automation. It’s the most common CI tool on the market with a large community …
Chose Jenkins
We went with drone.io ultimately for its first class support for container based workloads.
Chose Jenkins
We considered using Gitlab, but after some comparing, we found Jenkins was better in every way!
Chose Jenkins
Chef and Puppet Pipelines (formerly Distelli)
Best Alternatives
Apache ArchivaJenkins
Small Businesses
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.8 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.8 out of 10
Enterprises
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache ArchivaJenkins
Likelihood to Recommend
8.0
(0 ratings)
6.8
(0 ratings)
Usability
-
(0 ratings)
6.6
(0 ratings)
Performance
-
(0 ratings)
8.9
(0 ratings)
Support Rating
-
(0 ratings)
6.6
(0 ratings)
Implementation Rating
-
(0 ratings)
6.0
(0 ratings)
User Testimonials
Apache ArchivaJenkins
Likelihood to Recommend
Well suited for small organizations to medium-sized teams/organizations. Apache Archiva is well suited for:
  • It acts as a central repository/proxy of the artifacts generated and used by the teams.
  • It provides control on which open source repositories can be utilized by the team.
  • Saves network bandwidth by reducing outbound traffic.
Apache Archiva is less appropriate for organizations where immediate support/bug resolutions are required.
Read full review
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review
Pros
  • It's an open source project and therefore saves cost.
  • It allows exchange of artifacts/libraries between different teams.
  • It allows managing internal and external repositories with ease.
Read full review
  • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
  • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
  • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Read full review
Cons
  • Muti-tenancy was hard to achieve.
  • UI can be improved. Its seems bit dated.
  • It is a bit tricky to setup.
Read full review
  • Jenkins can be vulnerable to security issues due to its open-source nature and the availability of many third-party plugins. There have been instances where malicious plugins have been discovered, and these can pose a significant risk to organisations.
  • Jenkins can require a significant amount of maintenance, particularly when dealing with plugin updates and compatibility issues. Maintaining a stable and up-to-date Jenkins instance can be a challenge for organisations with limited resources.
  • Jenkins' reporting capabilities are limited, and it can be challenging to extract meaningful insights from the data that Jenkins provides.
Read full review
Likelihood to Renew
No answers on this topic
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Read full review
Usability
No answers on this topic
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
Read full review
Performance
No answers on this topic
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review
Support Rating
No answers on this topic
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
Read full review
Implementation Rating
No answers on this topic
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Read full review
Alternatives Considered
  • Apache Archiva is a great choice for organizations with a limited budget.
  • Alternatives are expensive to acquire Archiva comes offers REST API(s) which allows the creation of customized UI.
  • With Apache Archiva, it is easy to manage the remote proxy repositories.
  • RBAC helps with managing user access to the repository.
  • Configuration can be achieved using UI and stored in archiva.xml.
  • Backup of configuration is quite simple.
Read full review
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review
Return on Investment
  • The impact of Apache Archiva on ROI has been positive. Since it is open source. It is free.
  • It has allowed teams to store artifacts centrally, thus leading to a reduced need for multiple servers
  • Security audits can be easily performed on the artifacts.
Read full review
  • We run about 30 test projects through Jenkins every day, multiple times a day; this allows us to focus on new tests rather than manually running all these tests.
  • We rely heavily on reporting capabilities and email notifications; we have some jobs that send emails every time they run so we know if there is an issue with any of our services.
Read full review
ScreenShots