Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.
- For more information about upgrading to GitHub Enterprise Server 3.0 or later, see "Upgrading GitHub Enterprise Server."
- For more information about configuring GitHub Actions after you upgrade, see the documentation for GitHub Enterprise Server 3.0.
Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
Einführung
GitLab CI/CD and GitHub Actions both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and GitHub Actions share some similarities in workflow configuration:
- Workflow-Konfigurationsdateien werden in YAML geschrieben und im Code-Repository gespeichert.
- Workflows umfassen einen oder mehrere Jobs.
- Jobs beinhalten einen oder mehrere Schritte oder einzelne Befehle.
- Jobs can run on either managed or self-hosted machines.
There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to GitHub Actions.
Jobs
Jobs in GitLab CI/CD are very similar to jobs in GitHub Actions. In beiden Systemen haben Jobs folgende Merkmale:
- Jobs contain a series of steps or scripts that run sequentially.
- Jobs can run on separate machines or in separate containers.
- Jobs werden standardmäßig parallel ausgeführt, können aber so konfiguriert werden, dass sie sequentiell laufen.
You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the script
key. In GitHub Actions sind alle Skripte mit dem Schlüssel run
spezifiziert.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
Runners
Runners are machines on which the jobs run. Both GitLab CI/CD and GitHub Actions offer managed and self-hosted variants of runners. In GitLab CI/CD, tags
are used to run jobs on different platforms, while in GitHub Actions it is done with the runs-on
key.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
For more information, see "Workflow syntax for GitHub Actions."
Docker-Images
Both GitLab CI/CD and GitHub Actions support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with an image
key, while in GitHub Actions it is done with the container
key.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
Weitere Informationen findest Du unter „Workflow-Syntax für GitHub Actions“.
Condition and expression syntax
GitLab CI/CD uses rules
to determine if a job will run for a specific condition. GitHub Actions uses the if
keyword to prevent a job from running unless a condition is met.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
For more information, see "Expressions."
Dependencies between Jobs
Both GitLab CI/CD and GitHub Actions allow you to set dependencies for a job. In both systems, jobs run in parallel by default, but job dependencies in GitHub Actions can be specified explicitly with the needs
key. GitLab CI/CD also has a concept of stages
, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in GitHub Actions with the needs
key.
Nachfolgend ein Beispiel für die Syntax in jedem System. The workflows start with two jobs named build_a
and build_b
running in parallel, and when those jobs complete, another job called test_ab
will run. Finally, when test_ab
completes, the deploy_ab
job will run.
GitLab CI/CD | GitHub Actions |
---|---|
|
|
Weitere Informationen findest Du unter „Workflow-Syntax für GitHub Actions“.
Scheduling workflows
Both GitLab CI/CD and GitHub Actions allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in GitHub Actions you can trigger a workflow on a scheduled interval with the "on" key.
For more information, see "Events that trigger workflows."
Variables and secrets
GitLab CI/CD and GitHub Actions support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or GitHub Enterprise Server UI.
For more information, see "Environment variables" and "Encrypted secrets."
Im Cache zwischenspeichern
GitLab CI/CD and GitHub Actions provide a method in the configuration file to manually cache workflow files.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
GitHub Actions caching is only applicable to GitHub-hosted runners. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“.
Artifacts
Both GitLab CI/CD and GitHub Actions can upload files and directories created by a job as artifacts. In GitHub Actions, artifacts can be used to persist data across multiple jobs.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
For more information, see "Storing workflow data as artifacts."
Databases and service containers
Mit beiden Systemen kannst Du zusätzliche Container für Datenbanken, Zwischenspeicherung im Cache oder andere Abhängigkeiten einbinden.
In GitLab CI/CD, a container for the job is specified with the image
key, while GitHub Actions uses the container
key. In both systems, additional service containers are specified with the services
key.
Nachfolgend ein Beispiel für die Syntax in jedem System:
GitLab CI/CD | GitHub Actions |
---|---|
|
|
For more information, see "About service containers."