kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity
This repository has been archived on 2024-04-08. You can view files and clone it, but cannot push or open issues or pull requests.
d7ddf315d9
dagger/docs/getting-started/1201-ci-environment.md
jffarge d7ddf315d9 remove unecessary comment. Instead use Github review 
Signed-off-by: jffarge <jf@dagger.io>
2022-03-28 12:05:15 +02:00

2.1 KiB
Raw Blame History

slug displayed_sidebar
/1201/ci-environment europa

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. You don't write YAML CUE - typed configuration with built-in formatting
  2. 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