Skip to content

Commit

Permalink
Minor usage changes
Browse files Browse the repository at this point in the history
  • Loading branch information
rfay committed Sep 11, 2024
1 parent 79b50c4 commit 66448a3
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions src/content/blog/ddev-in-gitlab-ci.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Using DDEV in GitLab CI"
pubDate: 2024-09-06
modifiedDate: 2024-09-06
title: "Using DDEV in GitLab CI Tests"
pubDate: 2024-09-11
#modifiedDate: 2024-09-06
summary: Run DDEV within your GitLab CI pipeline.
author: Jochen Roth
featureImage:
Expand All @@ -17,29 +17,29 @@ required to run the Website within the CI. Even e2e testing is easily possible (

The same DDEV config can be used locally (shared across the team) and within the GitLab CI.

On GitHub Actions this is already possible though [ddev/github-action-setup-ddev](https://github.com/ddev/github-action-setup-ddev).
# How can I run DDEV in GitLab CI?

# How to run DDEV in GitLab CI?
GitLab CI can use Docker in Docker (DinD). With DinD, Docker can run inside
the GitLab Runner using the Docker executor. With this setup, you can use DDEV in your GitLab CI setup.

Many of you might be familiar with Docker in Docker (DinD). With DinD, Docker can run inside
the GitLab Runner using the Docker executor.

To run DDEV, a Docker image with DDEV installed ([ddev/ddev-gitlab-ci](https://github.com/ddev/ddev-gitlab-ci))
and additional configuration is required.
**([ddev/ddev-gitlab-ci](https://github.com/ddev/ddev-gitlab-ci))** provides the needed Docker image and instructions;
Some additional configuration may be required required.

Depending on your setup it requires different steps.

* gitlab.com: Just works
* Self-hosted GitLab requires additional configuration for the Runner (`/etc/gitlab-runner/config.toml`)
* **gitlab.com** works with no additional configuration.
* **Self-hosted GitLab** requires additional configuration for the Runner (`/etc/gitlab-runner/config.toml`).

On GitHub, you'll find tested configuration examples for
On [ddev/ddev-gitlab-ci](https://github.com/ddev/ddev-gitlab-ci), you'll find tested configuration examples for

* [gitlab.com](https://github.com/ddev/ddev-gitlab-ci/blob/main/docs/gitlab-com.md)
* [Docker in Docker](https://github.com/ddev/ddev-gitlab-ci/blob/main/docs%2Fdocker.md)
* [Docker in Podman](https://github.com/ddev/ddev-gitlab-ci/blob/main/docs/podman.md)

Once you configured the runner correctly and extended the `.gitlab-ci.yml` with a dedicated
Once the runner is configured correctly and you have extended the `.gitlab-ci.yml` with a dedicated
DDEV job you are good to go.

The [GitLab project template for TYPO3](https://gitlab.com/gitlab-org/project-templates/typo3-distribution/-/blob/main/.template/gitlab-ci-project-template.yml?ref_type=heads#L10-42)
is using DDEV in CI already.

**Note**: On **GitHub Actions** you can do these things using [ddev/github-action-setup-ddev](https://github.com/ddev/github-action-setup-ddev).

0 comments on commit 66448a3

Please sign in to comment.