https://github.com/hashicorp-forge/nomad-pipeline
https://github.com/hashicorp-forge/nomad-pipeline
doormat-managed
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/hashicorp-forge/nomad-pipeline
- Owner: hashicorp-forge
- License: mpl-2.0
- Created: 2025-06-10T15:00:16.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-11-24T14:50:25.000Z (7 months ago)
- Last Synced: 2025-11-28T03:42:25.133Z (7 months ago)
- Topics: doormat-managed
- Language: Go
- Homepage:
- Size: 142 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Nomad Pipeline
An experimental workflow orchestration system built on top of
[HashiCorp Nomad](https://www.nomadproject.io/). Nomad Pipeline allows users to define, schedule,
and monitor multi-step workflows (flows) that are executed as Nomad jobs.
> **Note**
This project is the result of two hack week projects and is unsupported and unofficial.
### Docs
The documentation for Nomad Pipeline can be found within the [docs](./docs) directory. The
[examples](./examples) directory contains example flow definitions and Nomad job files.
### What Is Bad?
* Run logs are not periodically removed from the data directory
* Run state objects are not periodically garbage collected
### What Could It Do?
* Shared state across flow jobs, provided by Dynamic Host Volumes or suchlike
* Offer runners via the Nomad [libvirt driver](https://github.com/hashicorp/nomad-driver-virt)
* Identify and automatically upload end of pipeline artifacts
* Persistent pipeline runners that accept flow runs over a long-lived connection
* Storage backend HA locking