TrustRadius Insights
Jenkins has been widely used for various use cases, making it the go-to choice for building, testing, and deploying projects. Its …
Overview
What is Jenkins?
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…
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
N/A
Unavailable
What is Jenkins?
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.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
32 people also want pricing
Alternatives Pricing
What is CircleCI?
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…
What is Buildkite?
Buildkite is a CI and build automation tool that combines the power of the user's own build infrastructure with the convenience of a managed, centralized web UI.
Product Demos
CI/CD Pipeline Using Jenkins | Continuous Integration & Continuous Deployment | DevOps | Simplilearn
YouTube
Jenkins in Five Minutes
YouTube
12 Soft Pastel Techniques for Every Artist / PLUS Painting Demo
YouTube
DWTS - Troupe waltz demo w/opera singer Katherine Jenkins
YouTube
How to run Ansible playbook from Jenkins pipeline job | Ansible Jenkins Integration| DevOps Tutorial
YouTube
08 - Jenkins pipeline integration with git & maven | Jenkins Pipeline Tutorial
YouTube
Product Details
- About
- Integrations
- Tech Details
- FAQs
What is Jenkins?
Jenkins Video
What is Jenkins?
Jenkins Integrations
Jenkins Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
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.
Reviewers rate Performance highest, with a score of 8.9.
The most common users of Jenkins are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(442)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
Jenkins has been widely used for various use cases, making it the go-to choice for building, testing, and deploying projects. Its compatibility with GitHub has made it a popular option among users. One key use case is automating the build process, which has significantly reduced the level of effort required by engineers. By coordinating internal infrastructure teams with external development teams, Jenkins ensures consistent and automated deployments. It also proves invaluable in quickly bringing servers back up after power outages by running scripts. Another important use case is automating builds for different projects, reducing compilation time and allowing for sharing build scripts across repositories.
Jenkins plays a crucial role in code testing, documentation, code analysis, integration testing, and user acceptance testing. It ensures a smooth release process, performs feature builds, and handles deployments effectively. The software's strength lies in its ability to support continuous integration and automation. With its support for various technologies and platforms, Jenkins makes the development flow fluid. Additionally, it can easily scale out across multiple machines and support simultaneous builds, tests, and deployments.
Jenkins is commonly utilized as an R&D build and deploy pipeline, facilitating end-to-end and unit testing. It also finds extensive use in building and deploying AEM applications with separate instances for each project. Whether running API tests automatically or conducting automated UI tests, Jenkins helps streamline the quality assurance process. It is frequently employed to control builds for different environments such as dev, QA, and prod.
Organizations leverage Jenkins to automate CD/CI jobs across various applications, enabling automatic testing and deployment. It proves instrumental in building, testing, and deploying micro-service architectures at scale. Moreover, Jenkins generates reports and notifications throughout the process to improve efficiency and visibility.
With its flexibility in managing build servers and supporting cross-platform testing and automation tasks, Jenkins becomes an essential tool for code tests, configuration management, and test routine execution. It automates the CI/CD process by receiving commit events, building, testing, and deploying code seamlessly. Many organizations rely on Jenkins to deploy client projects in development and production environments, streamlining the deployment process.
Jenkins integrates with other tools and platforms such as SVN, GitHub, and Docker, providing a seamless workflow and enhancing productivity. It serves as a versioning system, storing build versions and facilitating code management. Furthermore, Jenkins assists in deploying applications to different environments while also aiding in server backups and restoration. The extensive range of plugins offered by Jenkins allows users to customize and enhance their experience with the software.
Overall, Jenkins has proven to be a straightforward and reliable tool for continuous integration once it is set up. It offers users the ability to test their code in a cloud environment, mimicking a production setting and facilitating faster deployment. With its robust features, Jenkins also serves as a versioning system, storing build versions and facilitating effective code management.
One of the key advantages of Jenkins is its seamless integration with other tools and platforms. It seamlessly integrates with SVN, GitHub, Docker, and more, allowing for enhanced workflow efficiency. This integration enables users to leverage their existing tools and workflows while incorporating Jenkins into their development process.
Furthermore, Jenkins is widely utilized for deploying applications to different environments such as development and production. Its ability to handle server backups and restoration is invaluable for maintaining data integrity and disaster recovery.
Additionally, Jenkins provides extensive reporting capabilities throughout the build and deployment process. This improves efficiency by providing visibility into each step of the pipeline, allowing teams to identify and resolve issues promptly.
The wide range of plugins offered by Jenkins enhances its functionality and allows users to customize their experience based on specific project requirements. This flexibility makes it a versatile tool that can be tailored to meet the needs of different teams and organizations.
In conclusion, Jenkins has established itself as a trusted solution for building, testing, and deploying projects across various industries. Its compatibility with popular platforms like GitHub combined with its automation capabilities make it an ideal choice for any organization looking to streamline their development process. By automating tasks, reducing effort, improving collaboration between teams, and providing crucial reporting features, Jenkins empowers teams to deliver high-quality software efficiently.
Automated Build Process: Many users have found the automated build process in Jenkins to be great, emphasizing its efficiency and reliability. They appreciate the seamless automation of tasks, from compiling code to deploying applications, without human intervention. The ability to run code against any testing suite and automatically rollback faulty programs has been particularly valued by reviewers.
Supportive Community: Jenkins has garnered praise for its extremely supportive community that readily offers assistance and troubleshooting guidance. Reviewers have specifically mentioned how valuable it is to have a strong network of experienced users who are willing to share their knowledge and help others overcome challenges.
Connectivity with Multiple Clouds: Users highly value Jenkins' support for connectivity with multiple clouds, including Azure, AWS, GCP, OCI, and more. This feature enables them to deploy applications across different platforms seamlessly. Several reviewers have expressed their satisfaction with this flexibility as it allows them to leverage various cloud services based on their specific needs.
Confusing and Outdated User Interface: Several users have criticized Jenkins for its confusing, outdated, and visually unappealing user interface. They feel that the interface could be improved with a more modern design using the latest UI technologies.
Difficult Setup Process: The setup process of Jenkins has been described as difficult by some users, particularly when it comes to configuring it to successfully run software builds and managing dependencies. This complexity can be frustrating for new users who are trying to get started with Jenkins.
Frequent Logouts: Users have experienced frequent logouts while using Jenkins, which can be irritating. This interruption in their workflow hinders their productivity and adds unnecessary frustration.
Users frequently recommend Jenkins as a helpful tool for new users, as it aids in avoiding issues. They believe it is an amazing tool for CI/CD and suggest using it in conjunction with GitHub. Many users argue that all projects should implement Jenkins and recommend using it for managing releases. Furthermore, they highlight Jenkins as a powerful tool for achieving continuous integration and strongly recommend its use, given its proven track record. Overall, Jenkins receives positive endorsements from users due to its user-friendliness and effectiveness in streamlining development processes.
Attribute Ratings
Reviews
(1-25 of 28)Companies can't remove reviews or game the system. Here's why
June 28, 2023
My choice is Jenkins, for pipeline deployment!
We used Jenkins to implement deployment automation through CI/CD
pipeline. Deployment has been easy now. We were building and deploying
our applications manually into DEV, test and PRD environments. It was
time consuming and it involved repetitive tasks, we used the jenkins to
remove all these manual tasks.
- Automated build package
- Automated deployment
- Automated job run
- Performance improvement
- Handling plugins is difficult
- UI is outdated
May 22, 2023
Jenkins - review.
We utilized Jenkins to enable Continuous Integration and Deployment on 100s of our microservices. Deployed the Modular Pipelines architecture on Jenkins to enable seamless CI/CD between services utilizing different frameworks. So the thing is our pipelines facilitate the CI process from checking out code to building the artifact and then deploying it on Kubernetes.
- Used Jenkins as CI/CD tool.
- Extremely supportive community.
- Support connectivity with multiple clouds so the deployments over Azure, AWS, GCP, OCI and etc are supported.
- Trigger builds and deployments on Linux or Windows agents without issue.
- Support multiple version control tools.
- High memory utilization.
- Troubleshooting at times is hard as some plugins have bad error handling.
- Master/Agent connection must be more robust.
May 22, 2023
Jenkins-making deployments easy.
My company uses Jenkins for building, testing, and deploying our projects. Since you can have all these plugins and works with GitHub, Jenkins seems to be the obvious choice. Jenkins also offers code quality as it has plugins to check the code. This helps us as we know if the Jenkins run fails or goes below the score quality, then we can catch major problems before they are deployed.
- Building
- Code quality.
- Deployments
- Testing
- Documentation
- Logging
May 22, 2023
DevOps insights on Jenkins for CICD.
For nearly the last decade, we have used Jenkins as an automated build tool platform. My company does a lot of in-house app development. Like many other IT shops, Jenkins is a key component of continuous integration continuous deployment (CICD) pipelines. Allows us to schedule jobs automate film processes, deployment processes, server bounces, etc. It's capable of doing a myriad of options, anything from simply pushing a shell file to run token replacement, ant or Maven scripts, automated scheduled builds, on-demand execution, and trigger-based runs. We can even use it to interface with AWS for deployments to the cloud.
- It's fantastic at cutting down on manual steps for building and deploying ear and war files.
- Excellent tool for scheduling deployments.
- Trigger-based builds, such as when code is checked into a repository like GIT, are a strong suit of this tool.
- It can sometimes be difficult to navigate, especially when you're trying to drill down into configurations that are sourced outside of your job but referenced by the job you're designing.
We use it for our continuous integration. Builds are made every time a PR is merged into a master. It works pretty slickly, and when it's working perfectly, nobody needs to really think about it. It just does its thing. Jenkins is fairly straightforward and good once it is set up.
- Shows build progress.
- Shows error messages.
- Just works after being set up.
- Hard to get going.
- It can be hard to diagnose problems.
- Parts of it are not well designed.
December 11, 2021
Jenkins: Powerful Opensource Continuous Integration tool
We're using Jenkins as a Continuous Integration and Continuous Deployment tool in our organization, We are deploying, administrating, and managing multiple instances of Jenkins for a large number of teams. As it supports multiple kinds of Jobs and pipelines it's well suited to all the teams across our organization. By decommissioning enterprise CI Tools we started Using Jenkins and we're saving a significant amount of money.
- It offers multiple types of Jobs and pipelines which makes automation easier.
- We're using Jenkins as a CI tool, We are administrating and managing it for a large number of teams.
- Feature and functionality wise It's far better than all other enterprise CI tools.
- We have only community support so sometimes it can be problematic to troubleshoot or fix issues.
- Most of the plugins are developed and managed by open-source contributors so we've to rely on the mercy of collaborators or to develop our own.
- Sometimes it's very hard to troubleshoot the issues due to improper error handling in plugins.
August 09, 2021
Powerful but Difficult CI Solution
Jenkins is the frontline tool used by our Device Integrations team to ensure a smooth release process for each version of our app, whether that is doing a feature build for our QA team, uploading a new version for release day, or simply making sure each new PR builds and passes our test suite before merging into our main build branch.
- Full customization with a complete library of plugins and raw shell build steps
- Credentials handling with built-in storage
- Custom environments with locally hosted instances
- The UX is messy compared to other solutions
- Jenkins doesn't have the best method of storing job configs in its related repo, unlike GitHub Actions or CircleCI
- You can't easily set an environment variable for the rest of your job from within a build step, if at all.
August 03, 2021
Jenkins
Jenkins is used by my team to automate the build pipeline we have for our codebase. We use it to run builds on our code base automatically on a daily basis to help maintain the functionality of the code. It also automatically runs test cases for each push of code to our repository. It allows users to test their code in the cloud instead of locally and helps mimic a production environment.
- Jenkins is an open-source CI/CD tool with a massive community and lots of plugins and functionality.
- We are able to use Jenkins with multiple source code repositories and with various other tools.
- Jenkins has a very active user base and is very frequently updated to add features, security fixes, and other enhancements.
- Open source Jenkins has little in terms of formal support so it can be problematic to troubleshoot some issues.
- Jenkins plugins are created and supported by the community in most cases so you are at the mercy of the collaborators to maintain the code unless you want to join the effort yourself.
- There are a few popular software suites that are not fully compatible with Jenkins in their current state.
July 30, 2021
Jenkins!
- Jenkins is used for orchestrating automated test, CI, CD pipelines at our organization
- It is being used by a number of departments including engineering
- It solves a big need for us which is being able to deliver software and value to customers reliably.
- It is being used by a number of departments including engineering
- It solves a big need for us which is being able to deliver software and value to customers reliably.
- Automation
- CI
- CD
- Bloated and can be made more lightweight
- Hard to discover features and workflows
October 17, 2019
A CICD build tool of choice
Jenkins is used across various teams in our organization. It is an integration tool where we use the CI/CD pipeline for continuous deployments of our microservices. This tool makes life easy to automate the process of deploying services into all environments ( staging, production, and development environments). It uses in all development life-cycle processes including build, document, test, package, stage, deploys, static analysis, and publishing.
- It is free of cost.
- Easily configurable - Jenkins can be easily modified and extended. It deploys code instantly, generates test reports. Jenkins can be configured according to the requirements for continuous integrations and continuous delivery.
- Easy support - Because it is open source and widely used, there is no shortage of support from large online communities of agile teams.
- Most of the integration work is automated. Hence fewer integration issues. This saves both time and money over the lifespan of a project.
- Jenkins management is generally done by a single user and that leads to tracking and accountability problems with the pushed code.
- Jenkins doesn’t allow one developer to see the commits done by another team member, readily. This makes tracking the overall release progress a rather difficult job for larger projects. This can cause a lot of trouble with the release manager.
- Jenkins doesn’t provide any analytics (there are plugins but they are not enough) on the end-to-end deployment cycle. This again goes back to the lack of overall tracking that contributes to the lack of analytics as well.
October 16, 2019
Excellent CI/CD tool
We are using Jenkins for our CI/CD solution. It is used across all the departments in our org. we use Jenkins for various purposes. We use it deploying applications to various environments and taking the backups of the servers and restore them. We integrated Jenkins with various tools across the whole organization.
- Scalable
- Lots of plugin support
- Integrates with almost every tool
- Sometimes a bit slow
July 30, 2019
Effective CICD server
We use Jenkins as our main CICD server for multiple projects in our department and integrate Jenkins with our Gitlab source code repository and other tools such as SonarQube, Artifactory, Tomcat, Jboss, and Coverity. Our development team uses Jenkins jobs on every check-in code to run unit tests, scan code quality and run automation tests on every merge request before actually merging. Jenkins helps to increase our quality of product and eliminate most manual steps on deployment and integration.
- Flexible to create jobs in freestyle or pipeline.
- Supports various plugins to work with different programs such as AWS, Azure, Linux, Powershell, etc.
- Gives you a centralized location to manage all project pipelines and build information.
- Support various ways to trigger new jobs.
- Allows us to edit and retain files in the server and not override by repository.
- Support cluster to increase build performance.
- Jenkins UI is too simple.
- Does not provide a feature for backup and restore jobs.
- Lack of authorization rule - We could not assign separate users or groups to separate views or jobs.
February 07, 2019
Jenkins: The defacto standard build tool
Jenkins is our standardized build tool for all our software teams. It has allowed us to move to a standardized continuous integration development cycle rather than the ad-hoc build and deploy structure that was used in the past. Having the ability to manage all our builds from a single web platform has been great for the management of our build process. We now have the ability to easily pull build logs and to determine where individual builds we're deployed. Jenkins has been highly beneficial for our company.
- Manage continuous integration. It can be set up.
- Allows a single point of access for all our companies build information.
- It is also highly configurable and allows our individual teams to customize the builds as necessary.
- We have had some trouble with using Ansible with Jenkins to allow a 'pipeline' build. This points to a potential area Jenkins could improve by allowing a clean way to define build pipelines. It has the ability to define promotions to specific environments but the UI for that feature is not intuitive.
- There were a few examples where saving build configuration changes would not actually save the changes.
- Jenkins is a great tool, but the UI for the list of projects becomes hard to navigate when you have a large number of projects. It could use an updated design.
September 07, 2018
Jenkins as my Continuous Integration tool of choice
This tool made the development flow fluid. Standout features are the continuous integration and a variety of support offered for creating packages for a number of technologies like, Java, C#, C++, etc and across multiple platforms that makes releases easier for faster roll out of business functionalities . It also has hundreds of plugins that can help you setup continuous integration and continuous delivery tool chain in quick time. You can easily scale out Jenkins across multiple machines, and support simultaneous large number of builds, tests and deployments across multiple platforms.
- There are plenty of plugins available which helps us automate most of the jobs.
- You can do anything with Jenkins as there are a huge number of community plugins. There is a learning curve of course but after you've mastered it's quick sailing.
- The ability to schedule jobs on the go for your software build is very useful.
- I particularly don't like the user interface. There's a lot of scope for improvement. I would actually say a complete revamp is required.
- It is quite time consuming and not intuitive to create a job.
- The new build pipelines feature is good but needs to be refined and issues needs to be ironed out.
July 06, 2018
Automate anything and everything with Spinnaker
Jenkins is the tool we use for building our code, running our test cases and also for few of the inhouse datacenter deployments.
Apart from the regular CICD, we also use it for many of our other automation tasks, for example automating regular operational tasks like disk cleanup, log rotation etc.
Apart from the regular CICD, we also use it for many of our other automation tasks, for example automating regular operational tasks like disk cleanup, log rotation etc.
- Jenkins has plugins for achieving anything and everything.
- Jenkins is very flexible and has gone beyond just the CI capabilities.
- Very active development and frequent releases with new features and bug fixes.
- Very good authentication/authorization features with fine-grained access control.
- Sometimes installing the wrong plugins ends up with Jenkins in a non-startable state.
- When there is a huge number of builds, loading the Jenkins UI takes minutes. Sometimes times out as well.
- Lacking user level minute audit logging. It's difficult to find out which users installed/upgraded plugins.
- There were cases where jobs were in a hung state and could not be aborted as well. Jenkins restart was the only solution.
July 05, 2018
Jenkins at a glance
Jenkins is used for automating the build process of testing, deployment, and release. It makes continuous deployment faster and an automated process. It is used across the organization.
- Automated deployments. Developers manage their own code throughout the SDLC
- Jenkins workers can be easily scaled making multiple projects use the same Jenkins for deployment
- Easy setup of the environment using docker and Kubernetes
- Jenkins UI needs to be changed. It doesn’t utilize the modern web technologies
- Parallel builds should be displayed separately.
- Containers within containers for golang creates problems in dependency management
April 02, 2018
Jenkins CI/CD
We primarily use Jenkins as part of our build infrastructure for compile and build, typically executing mavens builds but also ant scripts for more complex tasks and workflows
- Is an excellent automation container
- Is excellent at integration with many other tools and services
- Is superbly well supported in the dev community with over 1k plugins
- Is very easy to recruit for, having high market penetration and lots of candidates with experience
- Has a number of security models to suit any enterprise or small user
- Is very scalable both horizontally and vertically
- History retention is an area that should improve
- Trend analysis should be better supported in the core product
- Dashboards need to be better provisioned in the core product
March 16, 2018
Automate your environment with Jenkins
Currently Jenkins is being used across the IT team in our organization. It simply does the hard job of automating all the repetitive tasks, includes details in projects, inside builds, follows workflows, accesses operating systems, and alerts when it's done, or, based on decisions during tasks, what to do. This reduced a lot of work for our dev teams, but also now is helping the infrastructure team and other departments. The knowledge of Jenkins utilization replicates really fast inside our organization as at least one people inside every team learned about or knows how to use it to build a simple job to automate a task, workflow or a deploy. Jenkins also allows us to monitor what's being done, helping managers and the team have an overview of how a pipeline is running. Another problem that Jenkins solved is centralizing automation. As it's controlled by a web console, it's easy to check what is being done, access logs of old jobs, view the entire console output and know exactly who and when a job was last executed. Also, you may set permissions by project, by job, or what you or your organization needs.
- Continuous Delivery
- Continuous Integration
- Automation
- Single Sign On
- User Interface
- Dashboards
February 28, 2018
Jenkins Review
It is being used by mostly the technology department. It allows us to run jobs between engineers and non-engineers. It increases productivity by automating processes.
- Automated scheduled jobs
- I think the UI is not the greatest.
December 14, 2017
JENKINS, OPEN SOURCE CONTINUOUS INTEGRATION TOOL
In our EAI department, we are using Jenkins to automate building and packaging TIBCO BW project.
Once the testing step is OK, the package is installed firstly in test environment.
Jenkins process is triggred each time a code is commited on SVN.
Jenkins can also serve as a versioning system because each time a build is made, its version is stored in Jenkins
Once the testing step is OK, the package is installed firstly in test environment.
Jenkins process is triggred each time a code is commited on SVN.
Jenkins can also serve as a versioning system because each time a build is made, its version is stored in Jenkins
- Graphical Interface.
- Possibility to use versioning system like SVN,CVS.
- We can execute quality code tool to check code quality.
- Easy to install.
- Version change too fast can sometimes cause instabilities with some plugins that have not been updated yet.
- In an open source context, coordination between different developers is often lacking; suddenly, it's sometimes a bit of a mess: new versions come out quickly, but they are not always well tested and regressions appear.
December 11, 2017
Jenkins is a flexible Open Source CI/CD tool.
Jenkins is one of the best open source Continuous Integration and Continuous Deployment tools. It is used in most of the projects in our company where we need a CI/CD pipeline. In the aspect of test automation, it is most helpful for the continuous executions whenever there is a new build.
- Provides good CI/CD pipeline
- Not a platform dependent, available for various operating system
- Huge list of plugins to integrate with many products
- Easily configurable and good documentation
- Results metrics could be improved to get good reports.
- Environment management can be improved, which is not quite straightforward.
- Initial setup and configuration will be challenging.
November 21, 2017
Why We Use Jenkins
Jenkins is a continuous integration tool on which my team relies heavily. My whole company uses Jenkins. It starts our build process, and goes all the way to start the code pipeline, from then our release goes from qa env, to e2e, and to production. Each job on Jenkins starts automatically when we push a new code to master.
- Continuous integration
- Zero downtime and automatic/scheduled jobs
- No manual effort
- Jobs can be turned enabled and disabled at any time with any configuration settings
- For my team in particular, we have some common accounts that we use, which makes it difficult to understand who initiated the job
- Could use a UI upgrade
- Don't have mobile flow
I used Jenkins to manage both development and release builds of software at my two previous roles (IBM and Red Hat.) In both cases, each department had its own instances, so that plugins could be customized and managed on a per-team, per-product basis. It enables teams to manage a fleet of build servers (slaves in Jenkins parlance) that can build source code and run tests in an automated fashion, across platforms - this enables cross-platform software to be tested against various versions of Windows and Linux, for example. It can also be used for simple automation tasks, though other tools like Ansible are better suited for those tasks.
- Minimal but extensible and flexible: Out of the box, Jenkins provides rudimentary capabilities to manage a host system with a framework for running build tasks and installing tools. There are many extension points available for plugins, and so a rich ecosystem of plugins is available. Many version control systems are supported, and integrations with other tools through plugins is excellent.
- Cross-platform: Supports many platforms and architectures quite easily, thanks to its implementation in Java
- Design focus: With Blue Ocean, you can get a nice-looking web interface for free
- Rich ecosystem: As Jenkins has been around for quite some time, there is a rich ecosystem of blogs, tutorials, guides, and documentation available for performing most of the day-to-day tasks you would need. There are also various vendors like CloudBees that offer hosted services.
- Ease of deployment: Jenkins can be deployed quite easily as a standalone JAR file. There are also system packages available for many Linux operating systems, such as Debian.
- Difficult to manage build configurations: builds are generally configured through the user interface, which is easier to modify (especially for casual users rather than dedicated release engineers), but this results in changes that can be difficult to track, especially if multiple people have write access to the system. Some teams manage this by restricting people that can modify builds, but this creates a bottleneck. Ideally, the system would provide a good audit trail and change history, allowing changes to be tracked and reverted easily. Competing offerings get around this by version-controlling their configuration (e.g. Travis CI, Drone, AppVeyor) but this results in a slightly higher learning curve.
- Quality of plugins varies widely: plugins are in various states of maintenance, and some are woefully incomplete and no longer updated. It can be difficult to know whether a plugin is well-written or not, or even actively maintained.
- Builds are often not easily reproducible: By default, builds are run on the slave systems, which can retain state between runs that cause difficult-to-debug failures. It's possible to get around this by using VM snapshots and periodically reverting to clean systems, or by using the Docker plugin to run builds inside ephemeral containers.
- Plugins are globally scoped: Because plugin versions and the Jenkins version are per-installation, companies with multiple teams typically run multiple instances of Jenkins. This leads to a maintenance nightmare and a lot of duplicated effort across teams keeping the systems patched, but is necessary because software requires different toolchains. It would be nice if Jenkins supported plugins on a "per tenant" basis, even though the running version would still be one-per-instance. Some platforms (such as OpenShift) get around this by running Jenkins inside a container, but that leaves out Windows slaves.
November 09, 2017
Jenkins helps automating everything manual
We have been using Jenkins across the company. The infrastructure provided by Jenkins allows us to automate our build process. The ability to work with numerous plugins makes it super easy to change various parts of the manual process to be fully automated. This reduces the level of effort engineers need to put in.
- UI for displaying test results
- Detailed logs
- Easy segmentation of build processes
- Make it easy to search logs across builds
- Provide wrappers to replicate jobs across multiple products
- Provide ability to export data
September 29, 2017
Jenkins - monkey that needs to be tamed
Jenkins is used as a default tool for continuous integration across the enterprise. We have multiple instances for different applications. The slaves are auto scaled depending on the demand for builds. Jenkins builds, deploys and tests our deliverables providing instant feedback when changes are implemented. We use a numerous number of plugins to support our choice of technologies
- Distribute builds across slave farm
- Extremely flexible e.g. pipeline jobs
- Open api which means it is easy to extend
- Integrates with other tools such as SCM or project management
- Plugins can clash with each other as they are not tested together
- Upgrades can be painful, again because of plugins
- Missing support for job templates, no useful plugins exist