I'm really curious what you and/or your company uses for CI/CD (and why, if you happen to know why the current solution was chosen over something else), whether it's one tool or a mix to cover the full process.
Are you using the tools provided by your VCS provider (Bitbucket / Github / Gitlab), Cloud provider (Azure Devops, Google Cloudbuild ...), the classics (Jenkins / Spinnaker), the Cloud Native bunch (Argo, Tekton, JenkinsX, Flux), plain old bash/Python scripts ... you name it (and please name it!)
Top comments (2)
We have a full Azure DevOps implementation. Their build agents are kept up to date, so we discover problems with tooling much earlier. When we need to scale build throughput, we simply need to purchase more agents, which is well worth the time savings.
As for the why, we were originally using TFVC and the on-premise TFS implementation. Now we are on our way to eliminating TFVC, moving everything to fine-grained git repositories. Azure DevOps seemed the logical choice for a migration, as we didn't have to do everything at once, and the user experience remained similar to our on-premise solution.
As for features, we heavily use Azure DevOps Repos, Artifacts, and Pipelines. It allows us to fully automate everything, with Artifacts allowing us to consume services and libraries produced internally.