At CircleCI, we’ve worked hard to build on-demand training to help our users get the most out of our platform and its capabilities. Historically, we created CircleCI Academy courses to ensure that all our customers know how to effectively use the features on our platform. Today, we’re taking a proactive approach to enhance your DevOps skills.

In our big series of Kubernetes anti-patterns, we briefly explained that static test environments are no longer needed if you are using Kubernetes. They are expensive, hard to maintain, and hard to clean up. Instead, we suggested the adoption of temporary environments that are created on demand when a pull request is opened. In this article, we will see the practical explanations on how to achieve unlimited temporary environments using Kubernetes namespaces.

Slack experienced meteoric growth between 2017 and 2020—but that level of growth came with growing pains. In his talk at the 2021 o11ycon+hnycon, Frank Chen (LinkedIn), a Slack Senior Staff Engineer, detailed one of Slack’s biggest pain points in that period: flaky tests. A flaky test returns both a passing and failing result despite no changes in the code. At one point, between 2017 and 2020, Slack’s flaky test rate reached as high as 50%.

Security scanning provides an opportunity to target, track, and trace vulnerabilities introduced to your packages as soon as Cloudsmith has received a complete package upload. However what happens when you want to intercept the results of a scan immediately. An early warning can make a difference when distributing vulnerable packages to hundreds, thousands, or even millions of developers, devices, or systems globally.

One of the key metrics IT leaders care about is the total time it takes for a release to go from development to being live in production. The metric used to measure that duration is called the “release lead time.” It can range from days to months, depending on factors such as team agility, enterprise constraints, and interdependencies.