Sometimes you need to test an OCI image in Kubernetes. Or perhaps you want to validate a new Helm chart to ensure it will deploy as expected. If you’re trying to build and test components for Kubernetes, Minikube can make that process easier.

Did you know that dev containers can have their own private Visual Studio Code extensions? By understanding some of the life cycle of the container, it’s possible to create and use extensions that are designed to support a specific dev container or Codespaces environment.

In most cases, we write a CI/CD workflow where all of the steps succeed. If a step fails, the job and workflow fails. But what do we do when we need the workflow to handle a failing step or job?

Every wanted to dynamically set (or unset) environment variables in your GitHub Actions? Needing more control over the configuration of your steps? Wanting to configure everything using logic written in the language of your choice rather than just relying on GitHub’s expression syntax? This post will show you how to use a powerful technique to take your workflows to the next level.

Continuing the topics from my last post, this week I want to offer a deep dive into the lifecycle of a Jest TestEnvironment by exposing the events that are raised when tests are run. I’ll also explore some of the details that are included with each event.