We are a midsize company, and we are using Jenkins as our CI/CD tool on Red Hat OpenShift. We anticipate to grow bigger and are planning to have multiple Jenkins per squad. We are fighting the battle of Jenkins on EC2 vs RedHat keeping in mind
1) centrally managing the Jenkins
2) Jenkins config as a code
3) Auto Scale
4) Disaster Recovery
5) Upgrading Jenkins and its plugins
Hi, since you are already using Red Hat Openshift so you are aware of how good Red Hat products are. Going with Red Hat will give you more flexibility considering points that you have mentioned. Red Hat products are based around an approach of providing flexible and scalable architecture where you can easily manage your instances in a cloud native manner. You can also have a look at Red Hat Ansible which will provide your team to run Infrastucture as a code. For Jenkins, you can easily set up and automate the things based on manifests file. You can also automate the things based on multiple environments.
If you're already on openshift, also take a look at openshift pipelines, which is based on Tekton. It's Kubernetes native and may make your life (LCM) a bit easier.
Codrefresh helps Increase build speeds, provide a game changing debugger, and a UI that is easy to navigate With legacy tech stacks slowing down software delivery, we help reduce friction and accelerate value delivery (according to our Social Gaming Partners) Customize Codefresh to your own needs, providing a leg up on the CD side (as well as the CI side) Codefresh is also an agnostic solution, so they will work with what you have without having to rip anything apart.