Jenkins

Avantages

La richesse des possibilités d'utilisation est particulièrement apéciable. Son intégration avec d'autres produits est aussi très utile

Inconvénients

La difficulté à programmer son utilisation et à mettre en place est un frein au début.

Avantages

what i like most is it provides wide range plugins.

Inconvénients

managing jenkins dashboard is little hard when we have too many jobs to be executed.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

The amount of information in the search results is significant, and it is easy to operate because it is free (easy to stop in case of emergency). A Docker agent and JenkinsX are also available, so they are compatible with the latest technology. Because it can be used not only on-premises but also with Kubernetes, it is helpful because the learned technology can be used for a long time, even if the stage changes.

Inconvénients

Since the configuration screen is displayed in a tabbed format, there are times when you cannot see what you want to edit unless you show it at the bottom of the browser screen.

Avantages

It was a revolutionary tool for Ci/Cd with a big community developing new plugins

Inconvénients

it's outdated compared to other tools and way to annoying to maintain

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

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.

Inconvénients

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.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

Jenkins is easy to deploy and use. The process for onboarding the users and designing pipelines and test automations are very straight forward. It does not need any specific training and the interface is intuitive and supports various programming languages.

Inconvénients

I cannot find any major drawback in jenkins. I personally feel the documentation that provided in the interface could be improved, so that the users doesn't need refer the documentation seperately.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

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.

Inconvénients

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.

Avantages

Jenkins is very simple to installation and configuration as standalone or cluster, just a few clicks to get Jenkins ready, it is flexible and easy to create Pipeline and Job from UI or by YML file. Jenkins support many plugins allows it easy to integrate with other tool and software such as AWS, Sonar, JMeter... and Jenkins support almost major language and OS.

Inconvénients

Jenkins UI is simple and it is hard for manage when we have a large number of jobs and pipelines. It does not have features for tracking job history, sometimes accident deletes or changes a job and we unable to recover it.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

I use Jenkins from 2 years now and is the best software con Continuous Integration and Continuous Deploy process. Have a lot of plugins integrated like as JaCoCo, sonar, maven etc. Develop and release are become very simply and automated with jenkins.

Inconvénients

The first Installation is not very simple, with docker can be improved. Any plugins have a problems with legacy version of Jenkins

Alternatives envisagées 

Pourquoi choisir Jenkins 

Pourquoi passer à Jenkins

Avantages

I've been using Jenkins for several years and find it extremely useful in solving any CI scenario from easy to very complex. With its rich library of plugins and active community, it's relatively easy to develop and debug pipelines. I like that some plugins provide embedded pages within builds for things like test reports, commit history, etc. Jenkins can also be easily integrated with a large number of external applications.

Inconvénients

In my experience with Jenkins, I find plugin management to be the most troublesome. It is often the case, that plugins are no longer maintained, lack documentation, or break things with upgrades.

Avantages

Jenkins provide easy build, pipeline, Version Control Management with ease of usability and control

Inconvénients

Understanding the failure logs should be simplified

Avantages

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

Inconvénients

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

Alternatives envisagées 

Pourquoi choisir Jenkins 

Pourquoi passer à Jenkins

Avantages

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.

Inconvénients

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

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

Allows creating simple as well as very customized Jenkins pipelines. Allows scripting using Groovy and shell scripts. Has tons of useful plugins , easily integrates with many other software systems. It hits the sweet spot between high customizability and developer friendliness if you stick to standard workflows. Complex customization of build pipelines is also possible.

Inconvénients

The ability to build very customized build pipelines is sometimes also a disadvantage. It's too easy to create a complicated pipeline with Groovy code which could be difficult to maintain. Also the Jenkins UI can be confusing for a novice user.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

First of all, it's an open-source tool. We need appreciate the efforts of Jenkins team. It's very stable and has a lot features on top of it. Also writing pipelines with groovy language is quite straightforward.

Inconvénients

Jenkins can improve the UI and its elements. It can provide more clear UI for the users.

Avantages

Jenkins plays a pivotal role in the DevOps toolchain, seamlessly integrating with other popular tools like Git, JIRA, Docker, and Kubernetes. It enables teams to automate and orchestrate their entire software development lifecycle, promoting collaboration and efficiency.

Inconvénients

Jenkins' user interface may feel outdated and less intuitive compared to more modern CI/CD tools. The documentation, while comprehensive, might require improvement in terms of organization and ease of use. New users may need to rely on community resources and tutorials to navigate through initial setup and configuration.

Avantages

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.

Inconvénients

I think interfaces are not simple and bit complex for me.

Avantages

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.

Inconvénients

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

Avantages

Creating pipelines will always work smooth like with Jenkins never had an issue with it in anyway whatsoever.

Inconvénients

Better visuals and graphics really. Its not the best looking but gets the job done.

Avantages

That it is an open source software that every development team can use, and contribute to the development of Jenkins itself

Inconvénients

That compatibility with other existing tools & legacy systems can be a huge issue. A company should check if Jenkins can be compatible with other tools they're using. A consideration in terms of setup efforts should also be made, because while Jenkins will certainly work for them, maybe a simpler alternative could be easier to implement, e.g. when they're already using GitHub or GitLab.

Avantages

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.

Inconvénients

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

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

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

Inconvénients

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

Alternatives envisagées 

Avantages

Makes it easy to deploy applications/services into different environments like DEV/QA/PROD. Easy to implement GitHub webhooks into job builds.

Inconvénients

Does not provide application monitoring or management functionality straight out of the box. Pipelines can be slow if configured incorrectly.

Avantages

Jenkins is one of the best automation tool for deployment. It’s easy to configure and maintain. The Jenkins implementation don’t need large code based enchantment to configure and implement it which makes it easy to opt. The build pipeline is easy to manage with it. Jenkins helps in boosting the agile process with automation which helps in speeding the delivery of the product. Jobs are easy to configure the build and deploy the code on multiple servers at once. Various third party pulgins give the wings to it. The large plugin community and easy plugin development make the process easy.

Inconvénients

Jenkins jobs configuration wizard should be more enhanced and should come with some more features which help to setup the jobs faster. Jenkins should also increase the documentation on the plugins development. Before updating Jenkins we always need to check its compatibility with the other plugins we are working with, this process should be simple.

Avantages

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.

Inconvénients

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.