Azure Kubernetes Service (AKS) vs. CloudBees Continuous Integration

AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.

Incentivized

For all continuous integration features like multi branch pipeline, continuous build, and deployment execution, highly customizable groovy scripting, well integration with most of repositories like SVN, GIT, etc. are some of the exceptional features which helps devOps related tasks a treat to work everyday. With some minor changes in agent configuration and handling of their configuration on master instances would reduce a lot of issues. Also, cache of maven handling on agents needs to be improved (though not related to tool but the CI pipelines). But, since this is a very mature and performant tool, we expect some out of the box functionalities to handle all such scenarios. Overall, the tool works wonders because of its highly customizable features.

Incentivized

• AKS makes it easier to replicate data to multiple regions
• Azure portal make it easier to manage the resources of the organization

Incentivized

• Customer Support
• Solutions engineering

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

• File or Workspace Management
• Agent configurations at master level
• Better Support for issues in product

Incentivized

As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.

Incentivized

Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.

Incentivized

CloudBees Jenkins Support is on par with the other enterprise tools we're currently using. It has performed well enough that we've adopted the product and placed it in the critical path of our software delivery pipelines.

Incentivized

• We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
• The resources on nodes need to be left out unused, so effectively it is wasting money there
• It definitely made us spend more time into maintaining kubernetes

Incentivized

• Positive - Handles number of requests
• Positive - Customizations of pipelines helps integrate many type of frameworks
• Negative - Cache management on agents for dependencies downloaded
• Positive - credential management helps reduce configurations to be done for each project job at manual level

Incentivized