One of the reasons we define items as code is it allows for the programmatic creation of resources. This could be for infrastructure, for the packages on your machines, or even for your pipelines. Like many of our clients, at Codefresh we are seeing the benefits of an “everything as code” approach to automation. One of the great things about defining different layers in the stack as code is that these code definitions can start to build on each other.

Webhooks allow for communication between services and APIs, which makes them the glue of our interconnected, cloud-based application environment. If you are familiar with APIs, you can learn to use webhooks. CircleCI offers a webhooks feature for our CI/CD platform that lets you subscribe and react to CircleCI events such as workflow and job completed. This tutorial showcases the webhooks feature and gives you steps for getting started.

Over the past 10 years, CircleCI customers have used our platform to customize their software development process. Orbs have helped standardize and scale CI/CD pipelines with reusable packages of configuration. The CircleCI API has allowed users to create robust internal tools for their developers and integrate with other products for more granular monitoring. As of today, CircleCI users have yet another way to react to events and customize their software delivery experience with webhooks.

Of the many challenges faced by modern enterprises, managing a remote workforce is near the top of the list. Keeping distributed teams organized, engaged, and happy is crucial in today’s highly competitive and globalized business environment. Providing reliable, secure, and cost-effective software tooling is just one piece of this increasingly complex puzzle.

In today’s world of software development, one of the most emphasized practices is CI, or Continuous Integration. Continuous Integration is the first step of the CI/CD pipeline and acts as an enabler for the whole DevOps mindset and methodology. CI is the foundation of modern software development. Given the fact that this is the first stage of a proper DevOps setup, it’s crucial that it must be done correctly.

This tutorial is a follow-up to TurboCharging your Android Gradle builds using build cache . The key focus of this post is the remote build cache, a build speed acceleration technology that can be implemented for both local and CI builds. This is a technology worth knowing about because: Gradle provides a build cache node available as a Docker image. You can host this image in a number of ways.