da8e8fbaac
So that we get auto-formatting and syntax checking in our code editor. The only snippets which have not been extracted are either terminal output, or file fragments (e.g. CUE) which are not valid standalone files. Resolves https://github.com/dagger/dagger/issues/1715 While at it, do a few fly-by improvements: - beta.1 -> beta.2 - add CUE & BuildKit links - up -> do Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2.1 KiB
| slug | displayed_sidebar |
|---|---|
| /1201/ci-environment | europa |
From local dev to 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:
- Instead of YAML, you write CUE - typed configuration with built-in formatting
- Configuration is executed in 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. We started with CI environments that you told us you are using. We will configure a production deployment for the same application that we covered in the previous page.
:::note If you cannot find your CI environment below, let us know via this GitHub discussion. :::
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
<Tabs defaultValue="github-actions" groupId="ci-environment" values={[ {label: 'GitHub Actions', value: 'github-actions'}, {label: 'CircleCI', value: 'circleci'}, {label: 'GitLab', value: 'gitlab'}, {label: 'Jenkins', value: 'jenkins'}, {label: 'Tekton', value: 'tekton'}, ]}>
If you would like us to document CircleCI next, vote for it here: dagger#1677
If you would like us to document GitLab next, vote for it here: dagger#1677
If you would like us to document Jenkins next, vote for it here: dagger#1677
If you would like us to document Tekton next, vote for it here: dagger#1677