Merge pull request #1884 from slumbering/issue#1761-docs-comments
[Docs] - content comments
This commit is contained in:
commit
9ba8b58dcd
@ -5,8 +5,8 @@ displayed_sidebar: europa
|
||||
|
||||
# CI/CD in your local dev
|
||||
|
||||
Everyone should be able to run their CI/CD pipeline locally.
|
||||
Having to commit & push in order to test a change is a slow way to iterate on a pipeline.
|
||||
Everyone should be able to develop, test and run their CI/CD pipeline locally.
|
||||
Having to commit & push in order to test a change slows down iteration.
|
||||
This guide shows you the Dagger way.
|
||||
Within 5 minutes, you will have a local CI/CD loop and run your first test & build pipeline.
|
||||
|
||||
|
@ -3,11 +3,11 @@ slug: /1201/ci-environment
|
||||
displayed_sidebar: europa
|
||||
---
|
||||
|
||||
# From local dev to CI environment
|
||||
# Integrating with your CI environment
|
||||
|
||||
Dagger can be used with any CI environment (no migration required) and has two important advantages which make the overall experience less error-prone and more efficient:
|
||||
|
||||
1. Instead of YAML, you write [CUE](https://cuelang.org/) - typed configuration with built-in formatting
|
||||
1. You don't write YAML, you write [CUE](https://cuelang.org/) - typed configuration with built-in formatting
|
||||
2. Configuration is executed in [BuildKit](https://github.com/moby/buildkit), the execution engine at the heart of Docker
|
||||
|
||||
This makes any CI environment with Docker pre-installed work with Dagger out of the box.
|
||||
@ -33,6 +33,7 @@ values={[
|
||||
<TabItem value="github-actions">
|
||||
|
||||
```yaml file=../tests/getting-started/github-actions.yml title=".github/workflows/todoapp.yml"
|
||||
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
Reference in New Issue
Block a user