Jenkins on Hardened Ubuntu 24.04 with Support

We use Jenkins on Hardened Ubuntu  within the company and do not recommend it to customers. I am currently using Jenkins on Hardened Ubuntu  mainly to avoid giving users access over the cloud portal.

Jenkins on Hardened Ubuntu is valuable for us from a continuous deployment perspective. We have created a job that allows end-users to start and stop AWS  or Azure  machines without requiring access to the portal. We give Jenkins  access to them, and they can manage their tasks as needed.

We have some jobs to copy files and perform other automated actions on Jenkins . Users can build the job, and their tasks are completed.

Jenkins on Hardened Ubuntu provides privileges to a few users, such as the infrastructure team, who have administrator roles, while others have access only to particular jobs with the appropriate ACL  privileges.

We have integrated Jenkins on Hardened Ubuntu with our Active Directory to measure security effectiveness.

Currently, Jenkins on Hardened Ubuntu is almost obsolete. Tools such as GitLab  now provide self-sufficient end-to-end deployment options. Azure DevOps  and AWS  with Bitbucket  are similar, and Jenkins is not beneficial for our code deployment perspective anymore.

Many SCM providers are highly capable for deployment, such as GitLab  and GitHub , which are sufficient for triggering jobs. I am not exactly aware of how Jenkins on Hardened Ubuntu can be improved since many are moving away from Jenkins.

Most of the plugins currently lack management. Our concern is that some security plugins should at least be maintainable by Jenkins rather than third parties.

I have been working with Jenkins on Hardened Ubuntu for more than eight years.

Since we are using an open source version of Jenkins on Hardened Ubuntu, we have never connected with Jenkins support.

Before using Jenkins on Hardened Ubuntu, we worked with some tools from a cloud provider, such as Argo CD.

My expertise is limited to Jenkins on Hardened Ubuntu and Argo CD. I would recommend the latter as a solution instead.

We have Jenkins plugins and other things for Jenkins on Hardened Ubuntu. There are many security-related plugins that need to be maintained, so some additional features could enhance Jenkins on Hardened Ubuntu's usability.

Jenkins on Hardened Ubuntu is easy to use. Since it is open source, it was highly recommended a decade ago and many organizations used it, but times have changed, and now everyone is shifting to other tools.

We are upgrading Jenkins on Hardened Ubuntu regularly. When a patch update comes, we apply it simultaneously with any available Jenkins updates, which helps us plan accordingly.

I rated this product eight out of ten.

I use Jenkins on Hardened Ubuntu  to manage and maintain Jenkins . It is used during conference events.

Regarding Jenkins on Hardened Ubuntu 's AI capabilities, I find its governance and security to be quite secure. The accuracy and reliability of Jenkins on Hardened Ubuntu's AI output is 90% accurate.

I have been using Jenkins on Hardened Ubuntu for seven years.

My advice to others looking into using Jenkins on Hardened Ubuntu is to go ahead and use it. I would rate this product an 8 out of 10.

My main use case for Jenkins on Hardened Ubuntu  is building pipelines for CI/CD and making sure that it has the proper security where the product that we deploy demands it.

The best features Jenkins on Hardened Ubuntu  offers are primarily centered around the security aspect of it, including a security baseline, the ability to set it up as a reverse proxy, and ensuring that it does not allow access to the internet or any other unwanted networks in the company.

The security baseline and reverse proxy setup of Jenkins on Hardened Ubuntu has helped my team by offering a reduced attack surface, meaning we can remove or disable any unnecessary packages. The agents are exposed only to the environments they need access to. Jenkins on Hardened Ubuntu node is built in the same hardened image. Troubleshooting is easier thanks to a more predictable OS behavior compared to a Jenkins  server running on a regular server with access by different teams, and we have a better compliance posture.

Jenkins on Hardened Ubuntu really helped me out in a specific deployment scenario by having a lot of different plugins and being a tool that has been around for a very long time. For continuous integration pipelines, it can be used in a number of different ways, whether it is deploying Kubernetes  containers or deploying C# code in Azure Functions , as it can handle pretty much anything thanks to the number of extensions and the community around it.

One area Jenkins on Hardened Ubuntu could improve is role control, particularly with RBAC permissions, as this has been an issue for a long time. While some plugins have helped in the past, they are now out of support, making it hard to establish a proper RBAC setup and integrate with SSO , MFA, and similar security measures. Adding some observability with more logs and traces would also be beneficial.

I have been using Jenkins on Hardened Ubuntu for about five to six years on and off.

Jenkins on Hardened Ubuntu is stable.

Jenkins on Hardened Ubuntu's scalability is acceptable, but nothing fancy, as it is an old product.

I have never used customer support for Jenkins on Hardened Ubuntu, if there is any.

I used Azure DevOps , CircleCI , and other tools, but I did not switch per se; they were just used in a different project.

Before choosing Jenkins on Hardened Ubuntu, I evaluated Azure DevOps  and CircleCI .

My advice to others looking into using Jenkins on Hardened Ubuntu is that if you really have to use it, it is a good option to give it a try. I would rate this product a 7.

My main use case for Jenkins on Hardened Ubuntu  is for the deployment of my microservices, creating the pipeline when creating the new services, and we can deploy easily for microservices in any environment.

A specific example of a pipeline I've set up in Jenkins on Hardened Ubuntu  is when I need to go on the setting there and add our GitHub  repository URL so that it can fetch that particular branch or that particular code, and then I can write that configuration file in our microservices, such as what the steps need to be there, including some code coverage checking, Sonar  check, and some security checks, which we can do on our microservice configuration level, enabling it and deploying it by creating the new pipeline on Jenkins .

One of the best features Jenkins on Hardened Ubuntu offers is for deploying; we can independently deploy any microservices by just creating a pipeline using a few steps only, and that is one of the main features of Jenkins , allowing us to avoid any manual setup or other tasks, as we can also write some scripts for automation deployment.

When I mention writing scripts for automated deployment in Jenkins on Hardened Ubuntu, the kind of scripts that have been most useful for me include some TypeScript, as well as some script files for using Jenkins scripts written specifically for deployment, so during the deployment, there are certain steps that go through that script and it will deploy.

Jenkins on Hardened Ubuntu has positively impacted my organization by showing a lot of improvement; it reduces our time and increases our development process, and it helps a lot everywhere. The difference Jenkins on Hardened Ubuntu makes is significant, as the deployment process has gone from hours to minutes.

Jenkins on Hardened Ubuntu can have some enhancements; the UI can be more attractive, as it is just a normal layout right now, so we can have some kind of tiles and devise some separate area to choose that particular pipeline itself related to configuration and the pipeline, but apart from that, functionality-wise, it is good, though sometimes Jenkins is down when we are doing multiple deployments at the same time, which is one major issue.

I have been using Jenkins on Hardened Ubuntu for the last five to six years.

Jenkins on Hardened Ubuntu is a very good feature, supplying us with a continuous integration and continuous deployment process, allowing us to easily deploy frequent changes and test our features, so it is very helpful for us. There is nothing else about Jenkins on Hardened Ubuntu's features that I think is worth mentioning.