Apache Maven vs Jenkins

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Apache Maven

Stacks3.4K

Followers1.7K

Votes414

GitHub Stars4.8K

Forks2.8K

Jenkins vs Apache Maven: What are the differences?

What is Jenkins? An extendable open source continuous integration server. In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

What is Apache Maven? Apache build manager for Java projects. Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.

Jenkins can be classified as a tool in the "Continuous Integration" category, while Apache Maven is grouped under "Java Build Tools".

Some of the features offered by Jenkins are:

Easy installation
Easy configuration
Change set support

On the other hand, Apache Maven provides the following key features:

Simple project setup that follows best practices - get a new project or module started in seconds
Consistent usage across all projects means no ramp up time for new developers coming onto a project
Superior dependency management including automatic updating, dependency closures (also known as transitive dependencies)

"Hosted internally", "Free open source" and "Great to build, deploy or launch anything async" are the key factors why developers consider Jenkins; whereas "Dependency management", "Necessary evil" and "I’d rather code my app, not my build" are the primary reasons why Apache Maven is favored.

Jenkins and Apache Maven are both open source tools. It seems that Jenkins with 13.3K GitHub stars and 5.48K forks on GitHub has more adoption than Apache Maven with 1.74K GitHub stars and 1.28K GitHub forks.

Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Apache Maven is used by Zillow, Intuit, and Zalando. Jenkins has a broader approval, being mentioned in 1775 company stacks & 1527 developers stacks; compared to Apache Maven, which is listed in 305 company stacks and 142 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Jenkins, Apache Maven

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k

Comments

Detailed Comparison

Jenkins	Apache Maven
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.	Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	Simple project setup that follows best practices - get a new project or module started in seconds;Consistent usage across all projects means no ramp up time for new developers coming onto a project;Superior dependency management including automatic updating, dependency closures (also known as transitive dependencies);Able to easily work with multiple projects at the same time;A large and growing repository of libraries and metadata to use out of the box, and arrangements in place with the largest Open Source projects for real-time availability of their latest releases;Extensible, with the ability to easily write plugins in Java or scripting languages;Instant access to new features with little or no extra configuration;Ant tasks for dependency management and deployment outside of Maven
Statistics
GitHub Stars 24.6K	GitHub Stars 4.8K
GitHub Forks 9.2K	GitHub Forks 2.8K
Stacks 59.2K	Stacks 3.4K
Followers 50.4K	Followers 1.7K
Votes 2.2K	Votes 414
Pros & Cons
Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Lack of support 7 Limited abilities with declarative pipelines	Pros 138 Dependency management 70 Necessary evil 60 I’d rather code my app, not my build 48 Publishing packaged artifacts 43 Convention over configuration Cons 6 Complex 1 Inconsistent buillds 0 Not many plugin-alternatives

What are some alternatives to Jenkins, Apache Maven?

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

Gradle

Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Bazel

Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Related Comparisons

Some of the features offered by Jenkins are:

Easy installation
Easy configuration
Change set support

On the other hand, Apache Maven provides the following key features:

Simple project setup that follows best practices - get a new project or module started in seconds
Consistent usage across all projects means no ramp up time for new developers coming onto a project
Superior dependency management including automatic updating, dependency closures (also known as transitive dependencies)

Apache Maven vs Jenkins