18 anos ajudando empresas
a escolher o melhor software
Sobre Jenkins
Solução de integração contínua no local e baseada na Internet que fornece às empresas ferramentas para criar, testar e implantar projetos.
Personally what I think is the biggest value of Jenkins is the possibility to really customise any kind of process relatively easily. Also there is a big community of devs using it and lot of addons.
If two person tries to deploy the product at the same time, we come across with errors.
Filtrar avaliações (561)
Uso
Classificar por
Filtrar avaliações (561)

Release management system that gets the job done

Jenkins is a must for Devops Engineer
Comentários: It's one of the most important tools that I use every day while working as a DevOps Engineer. It has helped me in easing my job very much
Vantagens:
We can automate and configure almost everything using jenkins, it can be used to start/stop servers, backup dbs, build and deploy codes in the environments, etc.
Desvantagens:
The complete logs may not be visible from Jenkins, but still, the main error can be seen. I can't think of any other problems in Jenkins
Alternativas consideradas anteriormente:
Past its best
Vantagens:
In its time, Jenkins was an outstanding tool. It was my go to for automation or all kinds, not just continuous integration. I have successfully delivered several projects with it. Jenkinsfiles and JCASC have been solid attempts to improve the Jenkins experience over the years.
Desvantagens:
Jenkins is hard to operate, gives you fewer and fewer options for well-maintained plugins and it's relatively easy to break pipelines in hard to understand ways. I would not recommend using Jenkins now that there are so many better options. I have spent many hours in an organisation where it was the preferred tool, trying to make pipelines more reliable, build custom plugins and meet security standards. It can be done but other products have so much of that prebuilt, why spend the time!
Jenkins Review
Comentários: I've been working for more than 7 years on Jenkins for CI, CD and also some automatic tasks
Vantagens:
You can customize a lot of things and also create shared libraries and use JTE to simplify the work
Desvantagens:
You need to keep updating the versions and has a lot of security issues
Functional but becomes way too complex
Vantagens:
The software itself is stable, it runs well and is not too complex to install
Desvantagens:
The fact that pipelines are built either with a UI which makes the pipeline tough to read when you have lots of conditions. The groovy language can also be used to write pipelines, but really ?? Let’s use a more common scripting language for this, maybe Python or ruby.
Widely adopted and flexible open source tool
Vantagens:
Best open source that allows you to manage your jobs with the support for multiple plugins for free.
Desvantagens:
Time taking to setup few workflows. Updates are very frequent
Versatile program with important features
Comentários: An experience of average satisfaction, we did not like that we had to spend extra budget to hire a new software that would bring together the capabilities that Jenkins could not contain enough for our team to feel comfortable, but on the other hand we do accept that it has improvement systems that They improved our developed software.
Vantagens:
A program that in the team generated high expectations for generating build automation, where Jenkins can be configured to automatically execute software builds every time changes are made to the source code, this ensures that any new code integration is tested and verified instantly, making it easy to detect and fix early errors or compatibility issues.
Desvantagens:
Under support for Microservices, which in our case and given that our company Google operates at large scale, often with architectures based on microservices, Jenkins could not handle multiple projects and microservices simultaneously, not allowing independent and specific builds and deployments as required. We needed, in this sense, we had to use a program similar and added to the one we already had.
Alternativas consideradas anteriormente:
Jenkins for Web Developers
Vantagens:
Its open source which means free of use with no cost. It can easily catch bugs and automate the testing process, making it fast.
Desvantagens:
It can be tough to understand as a beginner if you are configuring complex build pipelines or integrating many plugins.
Alternativas consideradas anteriormente:
Industry standard tool comfortable to use
Comentários: Great tool for any size of the project team!
Vantagens:
Works with all types of projects, all sorts of indurstiesQuite easy to maintainPlugins available for all your needsIntegrated with Git
Desvantagens:
UI can be a bit more intuitive - sometimes it is hard to find where are specific features located
Great CI/CD Integration tool
Comentários: Great tool with lot of features having so many benefits around usage
Vantagens:
Great CI/CD Pipeline integration tool and first CI/CD tool for auto code deployment
Desvantagens:
the grrovy scripting required to set pipeline are time consuming
A great experience to manage your CICD pipeline
Comentários: A great experience to manage your CICD pipeline
Vantagens:
It is a great CICD tool, allowing easy integration with VCS tools, and jobs scheduling. Plugins are essential for its use
Desvantagens:
Upgrades sometimes get your system down and rollback is required when using On Prem
Alternativas consideradas anteriormente:
Most flexible CICD platform with
Comentários: I'm running multiple backup or VM configuration tasks. I like it, but I also see potential issues in the future. Because of that I will think about migrating to another solution in the future.
Vantagens:
I like it's flexibility. You can almost do whatever you want with it.
Desvantagens:
Plugins can be outdated, also documentation should be fixed. I also hate that there is no way to configure Jenkins with Database backend (everything is kept in files). Because of that there is no way to create multiple Jenkins instances.
Alternativas consideradas anteriormente:
Staple in the CI/CD pipelines automation
Comentários: As typical, the solution has been used successfully for all possible deployment targets from simple make builds into compiled artifacts, through packaging of (non-compilable) artifacts into npm, gems, pypy, docker images and rpms/debs. However with the move to Kubernetes clusters in lieu of simply VMs clusters, Jenkins becomes more of a hustle to implement properly.
Vantagens:
Easy to implement, easy to incorporate into infrastructure, great support due to years of presence and experience from developers garnered throughout the years. The UI gives options for both classic feature-full or simplified BlueOcean approaches. Extendable and working great with 3rd party's tools and solutions. Pipelines typically defined in code in Groovy/Java.
Desvantagens:
Java at its core so typical memory and disk usage issues can happen, but can be helped through containerised deployment of it.Debugging pipeline issues often means meandering throughout the code for software and pipeline alike since reported errors can often obscure true source of problems. Not exactly the best option for docker image builds without docker in docker container trickery or Jenkins on bare-metal/VM deployments
Alternativas consideradas anteriormente:
Simply the best
Comentários: I like working with Jenkin day in and out.
Vantagens:
Powerful CI/CD tool with so many extensibility options. Easily integrate with any technology. Be it .NET java node customize it as per requirement. Tag management and deployment Multi-branch support and deployment rollback strategy Docker image support. Integration with Third-party like Argo CD / Azure DevOps
Desvantagens:
there is an initial learning curve associated with it. you would need to know the groovy script and also know some technical details on jenkin syntax but en

Jenkins is great open source continuous integration tool for large scale applications.
Comentários: 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.
Vantagens:
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.
Desvantagens:
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.
Automate the software process
Comentários: I'm started learning jenkins last year and now I can use it without any hassle.
Vantagens:
This automates the software lifecycle processes like building, testing and deploying steps. There is a big active community where I can asks questions from and there are many tutorials I can follow. So I think anyone can start learning this and give it a try. There are plenty of tools that are integrated with jenkins to extend it operations.
Desvantagens:
I think interfaces are not simple and bit complex for me.
Defacto CI/CD standard
Vantagens:
It is easy to get started with a simple pipeline for your code.
Desvantagens:
Integration with plugins requires more knowledge than it should.

A great tool for deployment control
Comentários: We use Jenking along with BitBucket which is our main Git repository for version control. These tools are connected so that we use the master branch in BitBucket to switch and update versions between our different environments like DEV, Test and PROD.
Vantagens:
I like the fact that Jenkins is a really customizable tool for deployments. In your Jenkins jobs you can choose between deploying some of the features of your branch and also impose rules of deployment like what will be deployed first and last to check for dependencies and prevent errors.
Desvantagens:
There is nothing that I do not like in Jenkings. The UI is very simple and easy to use. The only thing I could say here is that some times the errors in the console output are not very straight forward in order to understand what component of the deployment really failed.

Best CI/CD pipeline Automation Tool
Comentários: Best CI/CD automation tool. We are integrating it with Blazmeter for automation load testing. We can track all deployment from console and also track log if we are facing any issues. It has best GUI which will update about each CI/CD pipeline state.
Vantagens:
Jenkins is best CI/CD pipeline automation tool. We are using this for all our project repository. It's syntax is very easy to learn. I am using this for regular pipeline deployment as well as the scheduled pipeline trigger based on the regular expression. It reads the mapping from jules file and deploy code to mapped environment.
Desvantagens:
No issue find yet. As per me it's best CI/CD automation tool.
"The Best" CI/CD solution available in the Market!!!
Vantagens:
1. First of all its open source and has a vibrant community2. Great plugin support3. Integrates well with Containers like Docker and Kubernetes4. Ease of pipeline management5. Reports are crisp and easy to understand6. Robust CI CD solution
Desvantagens:
No Cons so far. One improvement can be done is in its UI!!
Jenkins deployment
Vantagens:
Best tool for deployment process , it providers clear cut view of the deployment status
Desvantagens:
Sometimes the deployment status won't get updated fast
Hero of all the CICD tools alive
Comentários: Saves our timeIncresed our productivityAutomated so many daily tasksDeployment happens automatically without manual interventions
Vantagens:
Free open source toolTesting processContinous IntigrationContinous deploymentRelease process streamlinePipeline management
Desvantagens:
Web UI needs improvementNothing from functionality wise
Great DevOps tool
Comentários: Good, does deliver what it is supposed to
Vantagens:
Continuous build and deploy capability, it's integration with other tools like Nexus
Desvantagens:
Performance issues and familiarity issues requiring an expert to look into deploy failures
Alternativas consideradas anteriormente:
Great tool for your CICD needs
Comentários: 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
Vantagens:
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.
Desvantagens:
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
Alternativas consideradas anteriormente:
Must have agile tool - Jenkins
Comentários: If the project is being developed in agile methodology Jenkins is must have tool . It is open source also can be integrated with many other software and the best part is high level of automation can be achieved with use of Jenkins. CI/CD is one of the latest trends in the market and Jenkins make it possible to achieve.
Vantagens:
Jenkins is one of the most required tool if developer are working in agile methodologies model . Continuous integration and continuous delivery can be achieved with help of Jenkins. Where in developer can build the code test and along with it deploy . Also Jenkins make it possible to integrate with other software like git , jira which makes tasks lot more easier
Desvantagens:
At first users may find it difficult to navigate through Jenkins but it's only matter of time till they get used to it . Maybe the UI maybe be done little user friendly

Product Build Version Management and Ad-hoc jobs Scheduling
Comentários: Jenkins has been a great tool for maintaining build version and scheduling timely jobs
Vantagens:
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
Desvantagens:
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,