TL;DR: Our free plan is newly re-launched, giving teams access to more build minutes, larger resource classes, and our most popular features formerly only available on paid plans. Visit our sign up page to get started today. Our mission has always been to help teams deliver software faster and better, and today marks a huge milestone for development teams everywhere: we are proud to now offer the most feature-rich and most generous free tier for CI/CD on the market.

Let’s face it: Creating the optimal CI/CD workflow is not always a simple task. In fact, writing effective and efficient configuration code is the biggest hurdle that many developers face in their DevOps journey. But you don’t need to be an expert to set up a fast, reliable testing and deployment infrastructure. With a few straightforward techniques, you can optimize your config.yml file and unleash the full potential of your CI/CD pipelines.

CircleCI’s scheduled pipelines let you run pipelines at regular intervals; hourly, daily, or weekly. If you have used scheduled workflows, you will find that replacing them with scheduled pipelines gives you much more power, control, and flexibility. In this tutorial, I will guide you through how scheduled pipelines work, describe some of their cool use cases, and show you how to get started setting up scheduled pipelines for your team.

Data visualization is the process of translating large data sets and metrics into charts, graphs, and other visuals. The resulting visual representation of data makes it easier to identify and share real-time trends, outliers, and new insights about the information represented in the data. Using CircleCI webhooks, we can gather data on workflow and job events. In this tutorial, I will lead you through the steps to create a React-based dashboard to visualize this data.

Software applications consist of interconnected systems - each providing a specialized service towards the common goal of meeting a business need. As with any network, an efficient data exchange mechanism is key to its functionality, effectiveness, and responsiveness. In the past, data exchange was performed using polling requests. At regular intervals, a system would make a request to get the latest information or find out if there is an update to deal with.

JFrog has been hard at work behind the scenes restructuring how we share information with the developer community. We wanted to create a one-stop resource for developers who code in a variety of languages, with a focus on DevOps, DevSecOps, and cloud native technologies. So without further ado … let me introduce you to our new JFrog Community site!