This document is a WIP, it’s intended to describe the reasons that lead to design decissions in Dkron.
Execution results Dkron store the result of each job execution in each node.
Every time dkron executes a job it assigns it an execution group, genrating a new uuid and send a serf query to target machines and waits for a response.
Each target machine that will run the job, then responds with an execution object saying it started to run the job. »
Intro Plugins in Dkron allow you to add funcionality that integrates with the workflow of the job execution in Dkron. It’s a powerful system that allows you to extend and adapt Dkron to your special needs.
This page documents the basics of how the plugin system in Dkron works, and how to setup a basic development environment for plugin development if you’re writing a Dkron plugin.
How it Works Dkron execution execution processors are provided via plugins. »