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.

Security vulnerabilities and license violations should be found as early as possible and the earlier in the SDLC , the better. As part of the “ Shift Left ” vision, JFrog CLI and Xray now allow scanning dependencies directly from sources , on-demand, using a simple command line. This functionality allows benefiting from the same JFrog Xray vulnerability and license scanning capabilities, even before deployment to JFrog Artifactory.

The cloud native promise to be able to “build once, deploy anywhere” is nearly fulfilled. With containerization and Docker , we can build our applications and services for any environment, and set configuration at runtime. Well,… almost. Operating systems and apps still need to be compiled to execute on specific architecture types. Your software that’s been compiled for an AMD64 processor can’t run on an ARM-based machine, nor can one built for Linux run on Windows.

The DevOps, IT security and IT governance communities will remember 2021 as the year when the Software Bill of Materials , or SBOM, graduated from a “nice to have” to a “must have.” Around for years, the SBOM has now become a critical DevSecOps piece, which everyone must thoroughly understand and incorporate into their SDLC (Software Development Lifecycle).

Virtualization has been with us since the 1960s. In computer science terms, it is about as old as the hills. Yet this old-school idea has never been more relevant. We all know hardware is expensive. Despite the cost, many businesses squander their precious processing power. All too often, a “one server, one purpose” mindset leads IT departments to waste server capacity. With virtualization, we leave this myopic view of server management in the dust.

Modern software development teams use CI/CD tools to ship features quickly and rely on best practices like shift-left testing to find application errors before they become user-facing bugs. But you still face the risk that any code you deploy could contain errors that your testing did not surface. To help you deploy with confidence and mitigate the effects of a bad deployment, Datadog APM now provides Automatic Faulty Deployment Detection.