The evolution of our Agile Testing Days tutorial to apply the holistic testing model and succeed with continuous delivery| Holistic Testing with Lisa Crispin
The pace of software delivery continues to accelerate. With the rise of serverless computing, platform engineering, and now AI-assisted development,| The Serverless Edge
SQL & Orchestration Techniques For Functional, Idempotent, Tested, Two-Stage Data Architectures| DataKitchen
In our big guide on how to use ApplicationSets for Argo CD applications, we explained the best practice of having a 3-level structure for all manifests with a clear distinction between Argo CD Application files and Kubernetes resource files. In that article, we also outlined several anti-patterns that we have seen in the wild, meaning […]| Codefresh
I recently found out about Should I deploy today? and laughed. A humorous way of guidning us developers when we hesitate about deploying code to production. This one is extra funny on a Friday or Saturday. Every now and then, memes about (not) releasing code to production on Fridays appear on my Twitter timeline. There's even T-shirts for sale, with No Deploy Fridays printed on them.| Agile & Coding
TL;DR: Functional, Idempotent, Tested, Two-stage (FITT) data architecture has saved our sanity—no more 3 AM pipeline debugging sessions.| DataKitchen
GoodRx, a digital healthcare platform, has released the Lifecycle project as open-source code. Lifecycle is a complete solution for temporary/ephemeral environments. The project’s build process includes built-in support for Codefresh pipelines. Creating preview environments from a Pull Request with Lifecycle Lifecycle was conceived as an internal project back in 2019, and today it is released […] The post GoodRx Releases Lifecycle Solution for Ephemeral Developer Environments with Built...| Codefresh
A Kubernetes cluster with default configuration has access to only two deployment strategies: To get access to more advanced deployment strategies such as blue/green and canaries you need to use a dedicated Progressive Delivery controller such as Argo Rollouts. We have previously covered several basic and advanced scenarios for Argo Rollouts in our blog. Today […] The post Laser Focused Kubernetes Deployments Using Argo Rollouts and Header Based Routing appeared first on Codefresh.| Codefresh
The cloud ecosystem has reached a turning point. Tools for operators/administrators are now mature and can handle most day-to-day operations that deal with Kubernetes clusters. Finally, we can turn our focus to application developers and their needs. If you look at all the Kubernetes tools available, you’ll understand that most of them treat Kubernetes as […]| Codefresh
We’re excited to announce our new Codefresh GitOps Cloud offering that lets you bring your GitOps deployments to the next level. You get: In this blog post, we’ll dive into some of the key features of Codefresh GitOps Cloud. Multi-environment application promotions with Argo CD As more organizations adopt Argo CD, platform engineers need to […]| Codefresh
Two of the most popular guides we’ve written are the GitOps promotion guide and the ApplicationSet guide. Used together, they explain an end-to-end solution for organizing your GitOps applications and promoting them between different environments, while keeping things DRY by using application sets. Both of these guides use Kustomize. We offered some hints for Helm […]| Codefresh
Argo CD is the most popular GitOps tool for deploying applications to Kubernetes clusters. Many teams that move their applications to Kubernetes choose Argo CD for its powerful sync engine and intuitive dashboard. Argo CD is also fully open source, which means teams can freely install it on their private clouds, behind-the-firewall data centers, or […]| Codefresh
Learn the secrets to faster code reviews: How to deploy individual preview environments for each pull request using GitHub Actions and Kubernetes.| developer-friendly.blog
In this article, I want to challenge where software testing happens and suggest that most manual verification (desk checks, QA, demo) that is part of a team’s delivery lifecycle should happen in production itself, rather than in some staging or UAT environment. I have used this approach in several teams within medium to large organisations&ellipsis;Read the full post »| oooops.dev
