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
Jenkins
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
Jenkins
Free Trial
No
Free/Freemium Version
Yes
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
Jenkins
Considered Both Products
Jenkins
Verified User
Employee
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 …
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 …
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/G…
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 …
Verified User
Engineer
Chose Jenkins
Jenkins is very easy to use, open source tool. Its better for simple build and deployments.
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.
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 …
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 …
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 …
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 …
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 …
Jenkins is the only tool I would consider using for CTCI deployment. Its plugins make it easy to customize to any environment you can conjure up and will always be custom fit to your needs as a DevOps engineer. Other tools have better support but lack the customizability and …
Microsoft Azure includes Azure Pipelines as part of its suite of tools. It is an adequate tool but tends to be overly complicated. I find that Jenkins is a much simpler tool to use.