Jenkins on CentOS 10 Reviews

My main use case for Jenkins on CentOS 10 is CI/CD, Continuous Integration and Continuous Delivery, where I have pipelines to produce builds, test the artifacts, and eventually do the release.

Jenkins on CentOS 10 supports my continuous integration and continuous delivery process through the pipelines, where we run both unit tests and the regression chain, and eventually we get the verdict on the delivery quality for a potential release of that artifact.

Jenkins on CentOS 10 is the main orchestrator that currently helps us ensure, in an automated way, the quality of the product we are delivering.

Jenkins on CentOS 10 has positively impacted my organization by automating a large part of our deliveries, from generating the product build to the tests and eventually the delivery of the artifact.

This automation has impacted the team's results by providing more capacity for the teams to deliver. Things that used to be manual are now automated in Jenkins pipelines, allowing the team more free time to develop and implement things that really matter and add value.

The best features that Jenkins on CentOS 10 offers include flexibility, as both scripted and declarative pipelines are very flexible and allow us to have anything from the simplest to the most complex implementation of a given pipeline.

Regarding the flexibility of the pipelines and scripts, we have stages that run conditionally, depending on the artifact that is being built. This facilitates our projects and brings clear benefits to the team with a lean pipeline, as it does not necessarily run all the stages that might be redundant or unnecessary for that specific artifact.

The features of Jenkins on CentOS 10 are enhanced by the possibility of having several agents running and calling them through labels so that they are categorized. For example, for a given artifact I use agent X, and for another artifact I use another agent. This helps a lot. In addition, there is the possibility of having plugins integrated into Jenkins and into the pipeline, which makes everything much more powerful and flexible.

I give Jenkins on CentOS 10 a score of 8 because I see that some plugins are maintained by the community and are not actually supported by Jenkins. Jenkins could, in some way, have native integration with the main build and test tools, and so on.

I have been using Jenkins on CentOS 10 for approximately 10 years.

Jenkins on CentOS 10 is quite stable.

The scalability of Jenkins on CentOS 10 is relatively easy, as we add agents as needed and on demand, allowing us to scale agents up or down according to demand.

We have basically relied on community support for some occasional issues, which are not many, I must say.

We have already obtained a return on investment, as the lead time for deliveries ends up decreasing because the time that people from development teams previously spent doing manual tasks is now automated, allowing them more time to actually implement.

This automation is not only less error-prone for humans but also provides more free time to implement things that add value to the product.

On a scale from 1 to 10, I would rate Jenkins on CentOS 10 an 8 overall.

My advice to others considering using Jenkins on CentOS 10 is to think about the architecture and the real need before defining whichever tools are going to be implemented.

I mainly use Jenkins on CentOS 10 for deployment, performing deployments, and rolling out to dev, QA, staging, and production environments.

First, the application is built based on the image that is on GitHub, and we roll that image out to our environments. Our pipeline runs the tests, performs the build, checks test coverage, and runs the whole code quality process. In the end, it pushes the application to the environment where it is supposed to go.

The best features that Jenkins on CentOS 10 offers are the use of scripts and the deployment automation.

Each application requires a specific configuration, and having the freedom and flexibility to change and code the behavior of each pipeline is essential.

Jenkins on CentOS 10 has had a positive impact on my organization by improving speed, as the team can roll things out without having to watch manually. While the pipeline is running, we can do other activities. The result is speed and productivity.

Based on the time we wait for a deployment and the number of deployments, I believe the improvement is around 20%.

I don't think any improvement is needed; it is already good. It already allows customization and provides logs. I don't have suggestions.

I don't think there is any other improvement that could be made to Jenkins on CentOS 10, as I have already mentioned that I am satisfied.

I have been using Jenkins on CentOS 10 for about two years.

Jenkins on CentOS 10 is stable.

For me, Jenkins on CentOS 10 has always been stable. It depends on how it is configured and on the machine it is running on, and in the company where I work, it has always handled the workload.

Support for Jenkins on CentOS 10 is provided by the company's employees, so I believe it is good.

I am considering that Jenkins on CentOS 10 is not open source, because only the company's team works on it and there is no one responsible for Jenkins on CentOS 10.

Since it is something internal to the company, there is no external cost. The cost would be the time and the employees' salaries.

The choice was not mine, so it is indifferent to me.

On a scale from 1 to 10, I would rate Jenkins on CentOS 10 a 10.

I give the highest rating to Jenkins on CentOS 10 for exactly everything I mentioned earlier.

I think users should study Jenkins on CentOS 10, test it locally, create a local branch, and test it on their own machine to understand how it works, and then apply it in the company.

My main use case for Jenkins on CentOS 10 is deploying some projects.

A typical deployment pipeline for my team initially handled only manual builds, which was a little frustrating, so I tried to automate it by implementing CI/CD using Jenkins on CentOS 10 along with GitHub Actions, where I made a push to the Jenkins API to build. For the most part, I ran the tests inside GitHub, and recently I created a pipeline to test migrations and deployments using a multi-branch pipeline, which I think is the greatest example I can provide.

That covers my main use case; we also use Jenkins on CentOS 10 a lot for routines, such as scheduling some Python routines.

Jenkins on CentOS 10 has positively impacted my organization by making processes really consistent and faster, allowing us to use our time for more tasks. With all those steps and pipelines, we can do more thorough testing, which I think is going pretty well.

Although I don't have any specific numbers, I am pretty sure that releases are a lot faster now. Before, all I had to do was access the remote server, and after building on Jenkins on CentOS 10, we now only need one more step to use Docker Compose up, which we can automate when the code reaches the correct branch and passes tests.

The best feature Jenkins on CentOS 10 offers is the multi-branch pipeline, which I think is very useful for understanding how to do deployments with different branches coordinated in one job, handling all jobs and sub-jobs quite efficiently.

The multi-branch pipeline has helped my team manage jobs and deployments more easily. Instead of using the manual build, when a branch gets to development, main, or staging, they just click on build now. The process used to be too manual, and implementing this pipeline has made it work pretty well.

Jenkins on CentOS 10 also has great plugins which are very useful. I do not know all the plugins available, and I think I have more to search about them, but it is really good to have logs and histories about our builds and scheduling. This is something we might lose when using GitHub Actions, but with Jenkins we can retain it over time.

I think Jenkins on CentOS 10 could be improved with more known features and plugins because we have a lot of plugins in my organization that I do not completely understand, and we face numerous alerts and security notifications that I do not really have knowledge of.

I have been using Jenkins on CentOS 10 since I got to my actual company.

Jenkins on CentOS 10 is stable.

Regarding Jenkins on CentOS 10's scalability, I think it is pretty good; it handles our code well, and I have never encountered any significant problems.

I have not had any issues with customer support for Jenkins on CentOS 10.

I have not previously used a different solution; Jenkins on CentOS 10 was my first integration solution of this kind.

Jenkins on CentOS 10 is deployed in my organization as a private cloud solution, though I was not the one who set it up, so it is actually local on our server.

The return on investment is noticeable since we save time and need fewer people.

We do not have to assign an individual to handle deployments anymore because it is done automatically when the code gets merged and reaches the server.

Before choosing Jenkins on CentOS 10, I did not evaluate other options because I had never used any alternative before, but after starting with it, I did try to compare the differences between Jenkins and GitHub Actions.

On a scale of 1 to 10, I would rate Jenkins on CentOS 10 a nine.

I chose a nine because Jenkins on CentOS 10 is really helpful and saves a lot of time, but I deduct one point because I do not know all the features and plugins; there is still something for me to learn.

About Jenkins on CentOS 10's AI capabilities and the accuracy and reliability of output, I do not think I have used any AI features from Jenkins; my experience is limited to integrating some metric systems with AI while not using any native capabilities within Jenkins.

My advice to those looking into using Jenkins on CentOS 10 is to definitely try it out. It is a great tool to get familiar with, and once you look at the documentation and some tutorial videos, you find it very helpful, and I believe we all should use it.

For Jenkins on CentOS 10, we are mostly using it as a CI/CD pipeline to deploy our traditional applications on our healthcare platform.

Jenkins on CentOS 10 has impacted us positively, mainly because of the open-source nature. We don't need to pay for it, and we can customize it. We can run parallel jobs to reduce the amount of time taken for deployments, reducing it by approximately 40%. We run our own code and pipeline as code, and it gave us flexibility in controlling the pipelines and integrating other plugins.

Our build pipeline had multiple steps, and we identified certain steps that could run in parallel. By running parallel jobs, we were able to publish the front-end at the same time as other services, making all services available after the test cases passed. We measured this by comparing our teams' workflow. Teams were able to get changes to production by merging to a branch and publishing. We maintained that pipeline and were able to reduce our deployment times by approximately 20% compared to our manual deployments.

The best feature is the build capability, which we can optimize and customize. Customization of Jenkins on CentOS 10 is straightforward since it is open source, allowing us to easily build those components. Automations are available, and we can integrate it with Git. Docker integration is enabled, and the ecosystem is robust. Jenkins on CentOS 10 has multiple plugins available, so we can use and customize them based on security requirements. Parallel executions run effectively, and we can enable the runners and control them accordingly.

For our needs, we customize Jenkins on CentOS 10 for our builds. When we need to customize it for our own build pipelines, we write our own code and use those solutions. Plugins and integrations are valuable, particularly Docker integration and observability and monitoring integrations, which are very helpful for us.

Jenkins on CentOS 10 is somewhat dated when compared to other pipelines. I would suggest improving the build performance and using distributed agents instead of running every build on the controller. Caching the dependencies would reduce build times even further, which would be very useful. Additionally, security should be strengthened more, as we need to enforce role-based access controls and protect secrets. There are plugins that also need to be updated, as outdated plugins can create security risks. Improving the pipeline as code with the Jenkinsfile and reusing it would standardize those solutions more across projects. Enhancing monitoring capabilities to monitor CPU and agent availability would be beneficial. Automating the infrastructure to create Jenkins installations and configurations would be very helpful.

We must maintain these components and find solutions when improvements are needed.

We have not experienced significant stability issues.

We previously used a manual deployment method before switching Jenkins on CentOS 10 to a CI/CD pipeline.

Since we use Jenkins on CentOS 10 in a startup environment, it provided us with return on investment. We saved approximately 20% of the time we spent on manual deployments.

Jenkins on CentOS 10 is free, which makes it an excellent option. The cost aspect is fine for our needs.

We evaluated some options, including GitLab and GitHub Actions, but we chose Jenkins on CentOS 10 in the end.

I would rate Jenkins on CentOS 10 overall as an eight on a scale of one to ten.

From my perspective, Jenkins on CentOS 10 has both advantages and disadvantages. Based on that consideration, I chose an eight. There are areas for improvement regarding security, plugins, parallel executions, and monitoring. However, it maintains strong customizability with plugin availability and the pipeline as code function. It has valuable features that support its rating of eight.

Regarding governance and security, we have significant control. Since we customize Jenkins on CentOS 10 on our own, we must take care of governance and security. We ensure that everything remains up to date and protect against outside vulnerabilities.

Regarding accuracy, I would say more than 80% of the outputs are accurate, so we can rely on that.

We deploy Jenkins on CentOS 10 in our organization using both public cloud and on-premise solutions. For our public cloud deployments, we use Azure and AWS.

I would recommend trying Jenkins on CentOS 10 before making a commitment, as it is open source. If you want a reliable solution, Jenkins on CentOS 10 will be very useful for your deployments.

Our main use cases for Jenkins on CentOS 10 are that we run our CI/CD pipelines which are hosted in that particular Jenkins only. We use it for continuous integration and automated testing purposes, Docker image building, automated deployment, security and vulnerability checks, infrastructure automation using Ansible playbooks, and scheduled maintenance jobs such as nightly log cleaners and space backups. All of these things are configured in our Jenkins CI/CD pipeline.

The benefits of Jenkins in large-scale projects are primarily focused on CI/CD purposes. The top benefits are automation at scale where it automatically builds, tests, and deploys applications. Jenkins can use multiple agents to run jobs across different machines, which reduces the workload on the controller and enables parallel execution. Additional benefits include faster software delivery, centralized monitoring, and broad integration.

Regarding cloud integration, we have integrated Jenkins on CentOS 10 with Azure to automate application builds for infrastructure provisioning and container deployments. When a developer commits code in GitHub, it passes to Jenkins on CentOS Stream 10 where we perform the build, test, and scan. After that, we store the Docker images in Amazon ECR, and then we deploy the application from Amazon Elastic Kubernetes Services. Following deployment, we perform health checks and monitoring, which has made a positive impact.

The best features of Jenkins on CentOS 10 include continuous integration, pipeline as a code where we write code in the Groovy language and the pipeline runs automatically to perform our jobs, automation of CI/CD, the ability to schedule jobs using cron-style scheduling, access control, security, build history and logs, and Docker and cloud integration.

Pipeline functionality encompasses software delivery workflows, which involves moving software from the development or testing stage to the production server. Jenkins automates this task with the pipeline running on the CentOS Stream 10 server. The main software delivery workloads include source code management where we pull code from GitHub, building and compiling it, automating and testing it, package and containerization, and deployment and monitoring.

Regarding the Jenkins plugin ecosystem, I have used this in a product where I worked for three months. We integrated Jenkins on CentOS 10 with external tools to automate source code management, builds, testing, security scanning, Docker image creation, and monitoring without having to build every feature from scratch.

In assessing Jenkins on CentOS 10's reporting capabilities, the build duration reporting is very good, and the queue length reporting is also very good where the number of jobs determines the waiting time for execution. Additional reporting metrics include queue wait time, build success rate, build failure rate, CPU utilization, memory and Java memory heap utilization, and disk utilization.

We can benefit from reusable Jenkins file templates and shared libraries so we do not need to write them repeatedly. We can enhance build efficiency with caching dependencies and reusing artifacts. Additionally, we can back up the Jenkins on CentOS 10 configuration and test restoration for reliability. During deployment, we can add more advanced health checks and rollback procedures. Regarding cost optimization, we can improve resource usage by staying within appropriate size limits and using ephemeral build agents.

We have been using Jenkins on CentOS 10 for four years.

I have not faced any crashes or performance issues with Jenkins on CentOS 10.

I find Jenkins on CentOS 10 to be scalable.

We use only Jenkins. In another project, I worked for three months where we used GitHub Actions.

The setup of Jenkins on CentOS 10 is straightforward.

In comparing Jenkins on CentOS 10 with GitHub Actions, Jenkins offers self-hosted and managed setups, while GitHub Actions is only GitHub-hosted. Jenkins requires installation and maintenance when self-hosted, whereas GitHub Actions is easy to start within a GitHub repository. The configuration files also differ as Jenkins uses Groovy-based configuration while GitHub Actions uses YAML language.

Jenkins on CentOS 10 is a very good tool for DevOps because it is an established tool with strong CI/CD capabilities. I highly recommend using Jenkins on CentOS 10 for CI/CD purposes. I have rated this product with a review rating of ten out of ten.

I primarily use Jenkins on CentOS 10 for managing complex build pipelines and ensuring smooth deployment automation. It helps us streamline our continuous integration and continuous delivery processes.

Recently, I used Jenkins on CentOS 10 for a major release where I needed to integrate numerous microservices and ensure seamless deployment. Jenkins on CentOS 10 played a key role in automating this, from testing to deployment, which saved us a lot of manual effort and time.

Jenkins on CentOS 10 automates several processes, particularly in our CI/CD pipeline. It makes the work much easier by automating testing, builds, and deployments, which significantly reduces manual intervention and errors.

Jenkins on CentOS 10 has made our organization more efficient and reliable. By automating repetitive tasks and reducing manual errors, we have saved time and resources, which we can now allocate to more critical tasks.

Jenkins on CentOS 10 has helped my team in Belgium with faster deployments and improved tracking of our software lifecycle. It has enhanced our overall process efficiency and product delivery timelines in the Belgian office.

I really appreciate the integral pipeline management features and desktop integration options that Jenkins on CentOS 10 offers. These make managing various tasks and processes very streamlined and efficient.

The pipeline functionality in Jenkins on CentOS 10 is valuable because it provides a comprehensive view of the entire build and deployment process, and it allows us to automate and monitor every step efficiently. This visibility and control enhance our workflow management significantly.

Stability in Jenkins on CentOS 10 could be enhanced. We look forward to improvements in the user interface and performance optimizations. Enhancing integrations with other tools would also be beneficial.

I have been using Jenkins on CentOS 10 for about six months.

On a scale of 1 to 10, I would rate Jenkins on CentOS 10 a 10 out of 10.

I give Jenkins on CentOS 10 a perfect score for its reliability and the extensive features it offers. Additionally, the way it manages CPU usage efficiently is a big factor for us.

My main use case for Jenkins on CentOS 10 is deployments.

For example, I configure Jenkins on CentOS 10 to access the repositories, and as soon as we have the repositories, we start creating stages. The pipelines can also include validations such as unit tests, code quality checks, and vulnerability scans.

Jenkins on CentOS 10 has a positive impact on my organization because it is useful, and we use it a lot.

This frequent use of Jenkins on CentOS 10 has brought concrete benefits to my team and to the company's results by enabling code quality.

Besides enabling quality and saving time, I have noticed another improvement with Jenkins on CentOS 10.

The best feature that Jenkins on CentOS 10 offers is the comfort of doing the deployment.

When I mention comfort in doing the deployment, I am referring to the automation and the linking with other tools, which make it much more comfortable.

Regarding the AI features of Jenkins on CentOS 10, I think its governance and security are great.

About the accuracy and reliability of the results from the AI features of Jenkins on CentOS 10, I think they are very good, and the security is very good.

I think Jenkins on CentOS 10 is good the way it is.

I am satisfied with the solution as it is.

I have been using Jenkins on CentOS 10 for about 5 years, since I joined the company.

Jenkins on CentOS 10 is stable.

The scalability of Jenkins on CentOS 10 is good.

The customer support for Jenkins on CentOS 10 is good, and it serves us well.

I would rate the customer support 9 on a scale of 1 to 10.

I did not previously use a different solution; I used Jenkins.

On a scale from 1 to 10, I would rate Jenkins on CentOS 10 overall as 80.

I chose that number because it is a very good tool.

Jenkins on CentOS 10 is deployed in my organization in a private cloud.

The cloud provider we use for Jenkins on CentOS 10 is OpenShift.

My advice to other people who are thinking about using Jenkins on CentOS 10 is that they can use it. It is a very secure tool that speeds up processes and links other tools in a very secure and easy way.