Note This article is orignally published at GitGuardian Blog. Before you quickly glance over the title and think “Oh god, yet another tutorial on how to give proper names to variables, how to use modules, how to manage states; nothing I haven’t already know” then close the tab right away, let me assure you this: this article is none of those. This “best practices” article aims to tell you something

1 What is Dagger? TL;DR: Dagger runs your CI/CD pipelines locally in a Docker container, and can run the container in any CI environment (as long as that CI can run a container, of course.) Do you want the long answer to this million-dollar question? It’s hard to answer, honestly. News is calling it a “DevOps platform”; the VC that funded Dagger even called it a “DevOps operating system.” But,

Yes, the title of this post isn’t bluffing: you can actually create a plugin for just about anything that takes your fancy. In my previous article, I walked you guys through DevStream’s codebase. If you haven’t read it yet, here’s a quick link for you: Hello, world! In this blog, we will walk you through the steps of creating a DevStream plugin from scratch with an example. What is DevStream

Hello, and welcome to the DevStream blog! In this very first “hello world” post, I will: give you a high-level picture of how DevStream functions; walk you through our codebase; explain briefly how to create your own plugin. If you haven’t heard of DevStream yet, please have a quick glance over our README. Without further adieu, let’s get started. TL;DR Too bad, there isn’t one. But don’t close the tab