Skip to content
Latchkey LogoLatchkey home
EnglishPortuguês日本語
Start Free

Latchkey Learn

Move your CI to GitHub Actions

Migration guides to GitHub Actions from Jenkins, GitLab CI, CircleCI, Azure and Bitbucket: how each concept maps and what does not convert.

Start here four stops, in order

  1. 01Azure template expression not allowedFrom another CI system
  2. 02GitHub Actions ImporterMigration tooling
  3. 03Azure Pipelines to GitHub ActionsFrom another CI system
  4. 04GitHub Actions to Latchkey CIMigration tooling

Contents 2 sections · 8 entries

Migration tooling 2 entries

GitHub Actions Importer and latchkey migrate.

  1. 2.1GitHub Actions Importer
  2. 2.2GitHub Actions to Latchkey CI
Explore other topics
GitHub Actions runners comparedEvery managed runner vendor, priced and benchmarked side by side. GitHub Actions costWhat Actions really costs, and how to cut it. Runner failures Latchkey repairsOut of memory, disk full, rate limits, lost runners: reproduced and fixed. GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed. Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners. Faster GitHub ActionsCaching, parallelism and cold starts, measured.