f53660772f
In the installer instruction for Windows it is claimed that the dagger binary is placed inside the System32 folder if permissions allow it, which seems to be no longer part of the install.ps1 script (and seems like a bad idea anyways). Signed-off-by: Jan Gräfen <223234+jangraefen@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| ci | ||
| client | ||
| cmd | ||
| compiler | ||
| cue.mod | ||
| docs | ||
| infra | ||
| mod | ||
| pkg | ||
| plan | ||
| plancontext | ||
| solver | ||
| telemetry | ||
| tests | ||
| util | ||
| version | ||
| website | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser.yml | ||
| .markdownlint.yaml | ||
| ci.cue | ||
| CODEOWNERS | ||
| doc.go | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| install.ps1 | ||
| install.sh | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| semver | ||
| tracing.compose.yaml | ||
Dagger
Dagger is a portable devkit for CICD.
Using Dagger, software teams can develop powerful CICD pipelines with minimal effort, then run them anywhere. Benefits include:
- Unify dev and CI environments. Write your pipeline once, Dagger will run it the same everywhere.
- Reduce CI lock-in. No more re-writing everything from scratch every 6 months.
How does it work?
- Automate actions with your favorite programming language. No proprietary SDK: just regular shell, Go, Javascript, Python...
- Reuse actions from a large and growing catalog.
- Tie it all together in CUE - a revolutionary declarative language invented at Google. No more YAML hell!
- Test and debug instantly on your local machine. No more waiting 10min to catch a typo.
- Run your pipelines on any Docker-compatible runtime, for maximum portability. This means most modern CI runners can run Dagger out of the box.