Dagger for GitLab
Dagger can now run your checks on every GitLab merge request, without a GitLab CI job or runner. The same checks run on your machine before push and on Dagger Cloud after push, with one cache.
Try it now
Set up Dagger for GitLab: 1. If needed, set up Dagger: https://docs.dagger.io/getting-started 2. Run `dagger cloud checks on`, so that Dagger Cloud runs my checks on every merge request. 3. Walk me through a test merge request, to verify that it all works.
Cut out the middleman
Since the first release of Dagger, many teams have used Dagger and GitLab together. After we launched integrations for GitHub and Entire, GitLab had to be next.
Dagger already ran your checks before push. Now Dagger Cloud also runs them after push, directly from GitLab events. You do not need GitLab CI, a runner or a .gitlab-ci.yml file.
Run dagger cloud checks on, connect your GitLab account, and choose your projects. Each push to a merge request runs the same checks as dagger check on your machine. Each check shows in the merge request’s pipeline, and “Pipelines must succeed” blocks the merge until they pass.
Scale without wasting compute
Dagger Cloud uses one cache for your organization, so an operation that already ran does not run again. You pay for CPU, memory, and data in and out. Idle time is free. See our pricing page for more details.
To give your agents the same cache, export DAGGER_ENGINE=cloud. When they push, checks that passed before push do not run again.
Debug without wasting tokens
Each check links to its Dagger trace. There, an agent sees the failed command, its output, its inputs and its container, instead of a job log.
Join us on Discord and tell us what you think.
Set up Dagger for GitLab: 1. If needed, set up Dagger: https://docs.dagger.io/getting-started 2. Run `dagger cloud checks on`, so that Dagger Cloud runs my checks on every merge request. 3. Walk me through a test merge request, to verify that it all works.