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
Best Alternatives
Apache ArchivaJenkins
Small Businesses
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.6 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.6 out of 10
Enterprises
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.6 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache ArchivaJenkins
Likelihood to Recommend
8.0
(1 ratings)
7.1
(74 ratings)
Usability
-
(0 ratings)
6.7
(8 ratings)
Performance
-
(0 ratings)
8.9
(6 ratings)
Support Rating
-
(0 ratings)
6.6
(6 ratings)
Implementation Rating
-
(0 ratings)
6.0
(1 ratings)
User Testimonials
Apache ArchivaJenkins
Likelihood to Recommend
Apache
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
Open Source
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
Apache
  • 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
Open Source
  • 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
Apache
  • Muti-tenancy was hard to achieve.
  • UI can be improved. Its seems bit dated.
  • It is a bit tricky to setup.
Read full review
Open Source
  • The UI could be slightly better, it feels kind of like the 90s, but it works well.
  • An easier way to filter jobs other than views on the dashboard.
  • An easier way to read the console logs when tests do fail.
Read full review
Likelihood to Renew
Apache
No answers on this topic
Open Source
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
Apache
No answers on this topic
Open Source
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
Apache
No answers on this topic
Open Source
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
Apache
No answers on this topic
Open Source
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
Apache
No answers on this topic
Open Source
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
  • 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
Open Source
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
Apache
  • 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
Open Source
  • Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement.
  • Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards.
  • Cost Savings: Jenkins is an open-source tool that is free to use
Read full review
ScreenShots