Operations | Monitoring | ITSM | DevOps | Cloud

Where do you usually track your code coverage? If you are not sure about the answer to this question or you would like to explore other options to the ones that you are currently using, then this post is for you. Specifically, this post details how you can use Codacy in your Codefresh pipeline to create and send coverage reports of your repository with every pipeline build. To follow along, make sure to have a Codacy and a Codefresh account. If not, now is the time to set-up a fresh account for free!

The appearance of containers and their performance benefits compared to the existing paradigm of virtual machines has forced several companies to rethink their software lifecycle, especially the delivery part. Continuous integration and deployment tools (CI/CD) are passing through a second renaissance phase which is characterized by new approaches centered around short-lived environments that are launched and destroyed in a much more dynamic way.

When I started working at Purple managing the E-commerce stack, I inherited a single AWS EC2 instance that represented our entire infrastructure. The problem was, the company was doubling in size every few months, and with this exponential increase in load combined with the issues we were already experiencing with this infrastructure, it became a large business risk.

The last year was undeniably a different year for everybody. At the start of 2020, Coronavirus spread all over the world, resulting in a global pandemic. Covid affected the way we live, work, meet other people, and has drastically changed everyone’s lives in ways that we could not ever imagine. In a world of uncertainty, DevOps has undeniably become even more important.

Coveralls is a web service that allows users to track the code coverage of their application over time in order to optimize the effectiveness of their unit tests. Once you are managing your application and associated resources within a CI/CD platform like Codefresh, you want to receive insights on the test coverage automatically with every pipeline build. This post provides an overview of how this can be achieved with Coveralls and Codefresh.

One of the most typical challenges when deploying a complex application is the handling of different deployment environments during the software lifecycle. The most typical setup is the trilogy of QA/Staging/Production environments. An application developer needs an easy way to deploy to the different environments and also to understand what version is deployed where. Specifically for Kubernetes deployments, the Helm package manager is a great solution for handling environment configuration.

Codecov is a code analysis tool with which users can group, merge, archive, and compare coverage reports. Code coverage describes which lines of code were executed by the test suite and which ones were not. However, this is not to be confused with a testing tool. Codecov does not run your tests, that is the job of your testing tools. The analysis that Codecov provides will classify code in either of the following states: Additionally, In this tutorial, we will.

What would you say if I would tell you that you can be as productive with the cheapest laptop as with the one you already have? Would you believe me if I would say that there is no need for you to install an IDE, compilers, CLIs, Docker, and whatever else you might have on your laptop? How about having a full development environment created whenever you need it instead of dealing with virtual machines and whatever else might be fulfilling your development needs?

DigitalOcean has just announced the DigitalOcean Container Registry, which is directly integrated into the DigitalOcean Dashboard. While you can use any Container Registry in your DigitalOcean resources, the goal of the Container Registry is to provide for easy connection between the Container Registry and DigitalOcean Kubernetes resources.

Progressive delivery is arguably the most reliable and advanced set of deployment practices based on a simple idea. Instead of shutting down the old release and deploying a new one in its place, progressive delivery takes an iterative approach. It gradually increases the reach of a new release. That gives us quite a few benefits like zero-downtime deployments, reduced blast radius, increased security, and so on and so forth. I will not go into depth about what progressive delivery is.