kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

apply more comments

Browse Source 
Signed-off-by: jffarge <jf@dagger.io>
This commit is contained in:
jffarge 2022-03-28 12:03:31 +02:00
parent 162e70cfd3
commit c4b16b91e1
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/getting-started/1201-ci-environment.md
View File

@ -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:
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: <!-- Is there a reason not to mention the catalog of actions / the fact that you can reuse actions and whole pipelines easily? -->
1. Instead of YAML, you write [CUE](https://cuelang.org/) - typed configuration with built-in formatting
1. You don't write YAML [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>