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

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

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

Inconvénients

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

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

Relatively straight forward to use once its setup and well tuned. Developers know it, and its easy to hire devops folks with lots of Jenkins experience.

Inconvénients

The access control story is still convoluted and requires attention. Easy to make mistakes. Setup is improved but still not as easy as newer competitors. Complicated pipelines are likely better suited to more modern tools

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

I like it's flexibility. You can almost do whatever you want with it.

Inconvénients

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.

Alternatives envisagées 

Pourquoi passer à Jenkins

Avantages

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

Inconvénients

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

Alternatives envisagées 

Pourquoi passer à Jenkins

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

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

The build monitoring and deployment automation are the key features for me. It also integrates well with version control.

Inconvénients

I like the quick build layout and UI better

Avantages

Jenkins allows us seamlessly switch back and forth between our clients to parse through their data.

Inconvénients

We only use Jenkins for one purpose and it allows for that, so there isn't any con that I have.

Avantages

Most of the IT companies are using jenkins to automate the SDLC that means automating steps like build, test and deploy. With jenkins we can build pipelines with customized workflows to automate. This gives high security and integrate with other tools like AWS and kubernetes. A very flexible tool that I use to enhance the quality of a software.

Inconvénients

I had to learn and ask from community to learn things. So for a new comer cannot use jenkins without a technical knowledge.

Avantages

Most of the IT companies are using jenkins to automate testing, building and deployment stages of the code. We can configure jenkins to automatically trigger these steps when code merge happens to the repository. If the deployment or build got failed, I go through the jenkins logs and find the issue. There's a big community support for jenkins and we can get tech help from them.

Inconvénients

Jenkins need considerable memory, CPU and storage resources of the server to run.

Avantages

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.

Inconvénients

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.

Avantages

Jenkins provides out of the box hundreds of plugins and it is very simple to build plugins to integrat to it. You can choose a development language of your choice and build a script to do whatever you need. It's simple as that

Inconvénients

As it have a high importance in the execution flow, it ends up having a status of superiority towards the operators that it builds as an aura, so it is common for people to feel afraid to operate it in the first moments and if the tool is not well configured with a well-defined authorities for users, it can actually pose a certain risk to the operation. But after it is well configured and after a few days of use, this aura is by passed and its use becomes utterly positive.

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

Building up Devops is very easy using Jenkins and get integrated with any existing build mechanism

Inconvénients

Jenkins visual appearance that could be improved and better organized

Avantages

Installation was easy, and the pipelines work religiously well. Executors handle Java memory allocation well. Love the plugins. You don't have to know how to write code to use some of the popular ones. I didn't use the cloud hosted option, but I know people who have who love it.

Inconvénients

Some of the authentication stuff is a little confusing, but if you're on a small team it's probably easier to keep your installation secure that if you use it for a large organization with oAuth or SSO.