Before choosing the solution I evaluated TeamCity and GitHub Actions.

We chose this solution because it is in line with the budget and customer preferences. 

We previously trialed an AWS-based product. However, it was complex to use and conflicted with some of our existing software.

We tried CircleCI and Concourse, but we went ahead with Jenkins.

We explored other open source CI tools like Travis CI and CircleCI.

We chose this solution because the deployment was right. We have to go further when it comes to the interface edition. Also, it's less when you are competitive with the travel CVA and the bamboo, and we will find the resources using Jenkins easily when it comes to the market level. So that's why we preferred Jenkins.

I looked into Travis, and I was primarily looking for customization. Travis wasn't as customizable as Jenkins.

No, we picked a long time ago before there were a lot of alternative options on the market. The few others available were expensive. Jenkins (well, Hudson at the time) was free!

Yes, we also looked at Hudson and Cruise Control.

We went directly to Jenkins.

We compared Jenkins to CruiseControl.

I was always choosing between Jenkins, TeamCity, Buildkite, and Bamboo. Most recently, hosted solutions like Codeship and Travis CI added to the list.

For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance.

For open source projects, Travis CI is standard.

We use AWS codepipeline + jenkins.

Before using jenkins + AWS, we used CircleCI.

Yes. CircleCI and TeamCity.

We also evaluated Bamboo but decided to go with Jenkins because it is open source and free.

We also looked at Buildbot.

No. When I started, Jenkins was broadly used.

BuildBot and CruiseControl.

We did not do a deep evaluation but we did look at Bamboo.

I didn't choose, but in my opinion, this is the best open source solution for CI and CD.