Jenkins has been a great tool for maintaining build version and scheduling timely jobs

Jenkins plays a important role in product development and deployment lifecycle, where a developer can build his code and give the build version to QA for testing, ones the build is tested it can be signed off and deployed to prod, Not one but many Different Applications can be created and can be built and maintain the build versions of each applications, Ad-Hoc scripts can be managed and can be triggered when required or schedule it in a timely manor, the jobs can be parameterised or non-parameterised, and can even set default parameter value, The scheduling of jobs are done using cron string, Usually we use linux shell scripts for job build configurations, it can also be done by many different ways. We can configure different executor machines for different jobs to distribute the load, Supports parallel processing of different jobs at the same time, User permissions are manageable (read, write, build etc.. ), It has lot's of native and third party plugins, for achieving different use-cases, and lot of community support, The features are well-documented inline, it has a great version control of the job configuration

Scheduling becomes little complicated if the job has to run in un uniform interval of time, for which we had to set up two jobs with the same build configuration and different cron scheduler, sometimes the application dropdown values disappears when used with different executors , Not a fully cloud-based solution, infrastructure should be managed internally, maintains limited build history,

I have used Jenkins for few projects with team members, we used it because we needed more flexibility at configuration. It is the only choice when you need more control over integration and testing. It is hard to configure and install but that is the trade-off for control over customization and configuration. Jenkins is free of cost itself although you need to server to host it. We use Jenkins only for projects which require more configuration and security.

Currently Jenkins is the only CI tool which has the largest set of plugins, it gives you more control over how it should work, like you can customize pipeline of continuous integration and delivery. There are plugins allow you to run Jenkins in kubernetes and docker but we never ran it on containers. Huge number of plugins available for Jenkins which allow you to integrate with other tools and customize it to your needs, plugins are available at Jenkins update center. Great thing about Jenkins is it work on windows, Linux and mac OS. Cost of using Jenkins is free because its open source although you need server to host it, you must maintain and update and that's your responsibility.

Jenkins is not easy to use you need to configure it and host it before using unlike tools like travis CI which is ready to be used. Learning curve is steep because it has lot of features and customization which is little bit hard at start. Hosting server is needed to host Jenkins, which means you also need to pay for hosting. Maintenance and updation is user responsibility.

I never encountered that something could not be done on Jenkins. Jenkins is very versatile tool for CICD purposes.

The UI is a bit complex and the learning curve is steep. The UI of the website has not changed much in last years making it look a bit out-dated.We usually highly under-estimated time spent on any workflow that needed to be done in Jenkins.

Basically I am Full Stack developer, But I am doing Testing, UI/UX, SEO and more because I am working in startup company. Jenkins is my first test tool and this last testing tool also because it's very easy to learn no need any experience to learn Jenkins. Second thing Jenkins didn't take more space in your laptop because it's run completely run in website just minimum setups only have in your system and more easy to integrate. My side opinion Jenkins don't have the drawbacks it's really very well of all testers.

The main reason to like Jenkins' is online interface, which offers integrated assistance and real-time error checking, makes it simple to set up and configure. The second thing it's very easy handle and they provide lots of plugins for pipeline project automation testing. Thirdly, there is The Continuous Delivery feature makes software delivery more dependable, automated, and efficient, which promotes better cooperation, quicker software releases, and higher-quality software overall. These are the reasons why I continue to use Jenkins

My side opinion Jenkins don't have the drawbacks it's really very well of all testers.

I would strongly recommand to consider Jenkins for your build machines. It's free, powerful and offers a lot of options that payed solution might not even propose.

Jenkins is fully open source, making it easy to install on almost any system. Jenkins comes with many different plugins that allows you to use it with your favorite Engine, versioning solution, etc... Jenkins offers many different ways of creating builds scenario, easy to understand steps, and strong scripting

It's not always easy to find support, and you might need to rely on your web searching skills in order to find some help. Updates can sometimes break plugins so you need to be careful with those. Luckly enough, there are ways to revert updates if necessary. It's not for Everyone, since setting up a server could take time and a lot of trial and errors.

Despite its one drawback Jenkins is the most suitable tool for process automation for most businesses. It requires a bit of specialised knowledge but is not so complicated as to require consultation with a specialist. The ability to set up chron jobs and the infinite flexibility in setting up jobs means that companies can use Jenkins to create the most custom-fit solution for themselves.

Jenkins has excellent process automation capabilities and extensive features supporting it. You can create pipelines and jobs to support CICD projects. You also have extensive flexibility to set up the ideal job fitting your needs. There are also integrations to the widely used version control solutions. Moreover, Jenkins can be used in other programs using groovy and other programming languages. Jenkins is also a locally deployable solution, making it suitable for preventing security threats.

The access control tools in Jenkins are inadequate for big projects with multiple levels of stakeholders. More often than not, this requires numerous instances of Jenkins running to prevent unauthorised access.

Jenkins is an absolutely great tool for CI/CD & testing of your source code repositories. It allows branching strategies to work seamlessly & enables administrator to give very specific roles to users as well. One of the best things I like about Jenkins is the ability to re-run any failed pipeline & simply removing the stages that are not required to be run again so it can focus on failed part only.

Jenkins provides best & seamless integrations with any source code repositories. It's very easy to get started with Continuous integration, continuous delivery & testing environment with Jenkins. It also has huge number of plugins to help create pipelines in a complex use-case. Can be easily integrated with slack or other messaging platform for alerts. Also allows easy scheduling & re-run for failed pipelines.

Feature wise Jenkins is great, but it comes with a very outdated UI which I just find ugly. Navigation & feature enablement can be rather easy if they work on their UI & make it up to mark with other alternatives like circleCI

Jenkins is one of the most known CI/CD tools on the market. It is outstandingly flexible and can be easily adapted to companies' needs without unnecessary concessions. The enormous number of plugins that allows various actions makes the usage incredibly adaptable. To tell the truth, sometimes plugins are deprecated and old, but the most important ones are quickly updated to the latest versions. Free and reasonably priced paid versions are a huge advantage on the market - it is one of the reasons for Jenkins being widely used across companies. Great customer support and documentation makes usage convenient. What is more, Jenkins has a big community that is actively participating in the project. If any problem occurs, it is probably resolved on the internet - in some forum or in the documentation. However, not everything is so great. The biggest flaw of Jenkins is its lack of intuitiveness. Because it contains a huge number of features, it may be too complex, especially for new users that do not have an experience in CI/CD. Also, the design is quite cumbersome and can look outdated. All in all, Jenkins is an amazing tool for CI/CD and I strongly recommend it to everyone who needs a flexible utility for pipelines management and monitoring.

Reasonable price/Free version Great flexibility An enormous number of available plugins Great customer service/documentation Widely supported by the community

Can be confusing The UI is not intuitive The design is cumbersome

Is widely used in the company and is very stable. maybe complex to manage, but is very good for CI and CD

Is the most used tool of the market, besides the open source to have a very active community.

I believe that only the UI could improve

Best in class, easy and fast to use and shows value quickly

Simple to use Highly configurable Largest Community Tons of free plugins for every issue ROI at its best

No built in support to backup/restore/DR of the product

I've been quite happy with Jenkins so far, as it allows us to have full control over our CI/CD infrastructure.

- free - extremely extensible - very configurable - cross platform - easy to get up and running - declarative pipelines - good documentation

- user interface got stuck in the 90's (there's still hope with blue ocean) - some more complex pipelines are not yet supported (e.g. nested parallel)

Jenkins is a great tool for DevOps professionals, and I am really satisfied with my experience.

It's very easy to integrate plug-ins for automated deployment and automated testing. It is easier to fix build and report errors in jenkins.

Jenkins doesn't come up with too many features out of the box, so managing individual plug-ins over time becomes difficult.

We can solve one of the major problems of the deployments as Jenkins can take of our major continuous build and integration process and it is widely used in all the major and minor enterprise applications and the Jenkins source code is very free and is flexible and can be used in almost all the operating system.

Best of Jenkins is it comes with wide range of the plugin suite and is used as the automation server software that can achieve continuous integration. It supports wide range of the operating system like UNIX,LINUX,Windows,etc. Good thing is it is open source and can we used with wide range of the major tools like CVS,GIT,ANT,Maven etc. Jenkins is easy to use and is very flexible. In jenkins we can integrate large number of the servers as a result team across the world can work continuously integrating the project.Jenkins helps the developers in customizing the tool.In all most all the enterprise applications these Jenkins are used as a main tool for the continuous build and integration tool.

The least about the software is that there is only the tracking on version control but there is no tracking on jenkins itself which is a major drawback. Cost of the Jenkins is unpredictable and may vary time by time. This Jenkins has another drawback as this does not allow the commit made by one person to be view by another person and tracking the Jenkins build process is bit difficult in large projects

We used jenkins as a CICD tool in almost every of our project. This works very well and has lots of plugins developed by community. It is highly customizable and I would recommend this tool for cicd use cases and if you are planning to introduce automation in cicd, this tool is the best

1. Open source and big community support 2. Easy to install, host and upgrade. 3. Supports wide range plugins for your every need. 4. Authentication and authorisation is well structured. 5. Easy to track the errors 6. Good and clean UI 7. Good capability in terms cicd as compare to competitors.

1. Sometimes job takes a lot of time and then gives error. 2. Machine configuration required high for better performance. 3. Plugins compatibility with jenkins version

As a Software Quality Assurance and Automation, my main job after writing and automating the tests, is being able to run the tests daily. When the test base exceeds ten test cases, it becomes difficult and time consuming to execute test cases daily. That's why I use Jenkins, as it allows me to run my test cases daily, and the best part is that I can run mobile and web test cases, and test cases that combine the two. I created a jenkins job to execute the tests daily, and send me and to my team the execution report by email. The report contains all the passes and fails and screenshots of the failed test cases, the consumed time and the percentage of the passed and failed. I simply couldn't find a better tool to execute automated test cases.

-The execution of the test cases on a daily basis -Executing mobile and web test cases -Recover the automation code from git for the test execution -The high quality reports generated by jenkins, that contain the time exeuction, the passes and fails, screenshots of the failed steps and the exact code line where the test failed -Configuring the email list where the report is sent -The easiness of use when it comes to checking the report -The free Jenkins documentation online On top of all, Jenkins is free :D

-It is very hard to create a Jenkins job for beginners

I am using Jenkins to implement our CI/CD processes and boost our development team productivity.

* Easy installation, it's really easy to install and configure, in a couple of hours you can have your Jenkins server up and running. * Cross-platform: You can have your Jenkins master on Linux, and your slaves in Linux/Windows. * It has a plug-in for everything. I am using plug-ins to integrate with Git/JIRA/Slack/Maven/Python/etc. * Manage Jenkins is easy and user-friendly. * You can configure your CI/CD pipelines, it's a very flexible tool. * Schedule jobs are easy to set and reliable, you can trust them to run scheduler tasks. * You can have your automation on Jenkins, once deployment pipeline is done, you can trigger your automation testing. It's great because you have everything in one single place and everything is coordinated.

*When Jenkins slave is installed on Windows as service, and your server receives a Java update, sometimes your slave will get broken. I have faced this issue several times, and it's difficult to debug what is happening. The best option is to uninstall the slave has service and re-install.

Jenkins enhance the product life-cycle with power of automation. Deploying multiple clients servers is a job of few hours now. The Jenkins community or support are the most relevant place to discuss your issues in Jenkins. The job fail notification come with the details of the right place to investigate the issue.

Jenkins is a powerful tool for achieving the continuous integration and delivery. Jenkins provide the various plugins to build, test and deploy the code. Implementing the application don't need any major code changes. Large scale infrastructure can be easily managed by the distributed Jenkins architecture to build and deploy the projects in faster way. The rich set of plugins help in setting up the jobs steps. The open source code of Jenkins provide the transparency about each module.

Jenkins should provide the recommendation of pipelines as per the product needs. View filters need more enhancement for customization and Throttle build plugins keep stopping in the latest update. There are a limited plugins for snapshot of configuration as I think it should be an in-build feature of Jenkins itself.

We visualized and streamlined our software release process thanks to Jenkins pipelines.

Rich set of functions that allow to schedule different software processes execution. Even more rich choice of plugins an ease to develop own plugin. We use Jenkins to streamline software we develop releases. We have changes signed daily for release and this is where Jenkins pipelines come to the stage. As soon as developer code is ready for review, it goes through automatic code quality checkup before other people start to review it. After review Jenkins takes care of the rest of phases such us preparing and deploying integration build and then safe roll out to our production servers

Not much options available for making backups. We also experienced serious issues when trying to perform major upgrade of Jenkins: the error was that Jenkins can no longer read job configs of older format (while we expected it converts all jobs automatically). As a result we need to perform a piece of manual work to perform an upgrade.

This tool made the business development flow very much easier. Best features include the continious integration with the multiple builds which makes releases easier for better business its installation is also much easier as jenkins is a self-contained Java-based program, ready to run out-of-the-box, with packages for Windows, Mac OS X and other Unix-like operating systems.So we are good with any environment we can use even in console based OS with its hundreds of the plugin the jenkins tool gets continuous integration and continuous delivery tool chain.Jenkins can easily distribute work across multiple machines, helping drive builds, tests and deployments across multiple platforms faster. It also acts one queue to queue TRANSFER tool which help in transfer of the messages from one queue to another based on build parameter that are being configured with it only sorts the messages based on parameter provided and make the messages reach best feature i loved in it

It requires effort and focused attention, but if you put that effort in you can do anything you need. Though you might find yourself stuck for a while the community support is great and somebody has probably already found a solution you are looking for.

Jenkins can be used for all steps in the CI/CD pipeline. It's flexible and not restricted to a single style.

Jenkins resource configurations can be hard to figure out at first. You have to grow with usage, and it's not just a quick out of the box solution.

Jenkins provided automatic building for 100s of software branches each month for like 7 years. Very stable and kicked ass.

We automated the heck out of Jenkins. Oh yes, when somebody checks in, Jenkins will build. However, we went way beyond that by detecting new branches in Source Control and establishing jobs for that new branch and later when the branch was closed (per our definition) we would be delete all the jobs. As a result, our internal customers didn’t need to “remember” to add jobs to Jenkins. We automatically detect and ran those jobs as they created new stuff.

As a user, Jenkins is very straight forward, but our automated job creation software was pretty complex and interfacing with Jenkins at that level was certainly not a normal user feature.

Jenkins make our life easy with removing the risk of manual errors and help in speeding the process. The Jenkins community is the best one stop place where you can discuss the stuff and get the solution. Once you adopt it you will surely feel the difference with the quality and fast delivery of the product.

Jenkins is an open source automation server that help in pure automation with continuous integration and help in fast delivery of the product. It is highly recommended with Java language application as it itself writing in it. The numbers of plugins make this tool special. We can also configure the mail notification on different events like build failed and unstable build. The best thing in it is easy to configure with the help of web interface where we can check the errors and other important notifications. The integration of Jenkins help in to deliver the product with CI/CD model.

Jenkins should come with the in-build backup option and I always keep missing it and adding the other third party software to keep maintain the backup before deployment. Multiple Jenkins jobs do need to setup in case of multiple language application is used by the product.

Most of the companies using jenkins to automate their software deployment steps. This reduce the repetitve tasks and saves out time a lot.

Jenkins is a powerful tool that we used to automate code building, testing and deployment. We use jenkins to create CI/CD tool for all of our projects. This integrated with most of the version control systems like git. Jenkins can be run on a single machine or multiple machines to enhance the scalability. User interfaces are very informative and we know where to navigate next.

Jenkins is complex to use without any prior knowledge. So new users need to know how to use it.

Pretty satisfied.

It's not to difficult to set it up. You can find plenty of tutorials online. We use it for continuous integrations, tests and deployments of our mobile apps and we are very happy with it.

UI could be more modern, but considering the price we can't complain :-)