123% flere rapporterede CVE'er pr. dag i 2026 end sidste år.

CI/CD-integration

Forbind dine repositories med en GitHub-app – CRACI bliver runneren under dine GitHub Actions-workflows, og hver kørsel vises stadig i GitHub

Forbind med en GitHub-app

Installér CRACI's GitHub-app på alle eller udvalgte repositories. Den forbindelse er hele opsætningen: CRACI kan derefter køre jobs for de repositories, du har valgt, og du bestemmer selv, hvilke det er.

Connect CRACI with a GitHub App The CRACI GitHub App is installed on all or selected repositories of a GitHub organization. CRACI can then run the jobs of the repositories you chose. Install the CRACI GitHub App Repository access for your organization All repositories Only selected repositories api-service web-app firmware sandbox CRACI runs the jobs of the repositories you chose You keep control of which repositories those are Runs, logs and checks stay in GitHub

Én linje pr. workflow

CRACI erstatter runneren, ikke GitHub Actions. Skift et job til runs-on: craci, så kører det på CRACI's runnere. Dine workflow-filer, actions og secrets bliver, hvor de er – der er ingen ekstra pipeline at vedligeholde.

GitHub Actions jobs on CRACI runners A GitHub Actions workflow sets runs-on to craci. Each job runs in its own isolated virtual machine on a CRACI runner, on Linux x86-64 or ARM64, hosted in Europe, and the run still appears in GitHub. .github/workflows/release.yml jobs: build: runs-on: craci was: ubuntu-latest CRACI runners Hosted in Europe Job VM build Linux x86-64 Job VM test Linux ARM64 Job VM publish Linux x86-64 One isolated virtual machine per job, 1 to 32 vCPU Runs still appear in GitHub About 2x GitHub-hosted speed

Kørslerne bliver i GitHub

Jobs, der kører på CRACI, vises stadig i GitHub, så kørsler, logs og checks på pull requests bliver der, hvor dit team allerede kigger. GitHub Actions-cachen virker som før, og CRACI-runnere bruger et fast egress-IP-interval til allowlists.

CRACI runs stay in GitHub Jobs that run on CRACI still appear in GitHub with their runs, logs and pull request checks. The GitHub Actions cache works as before, and CRACI runners use a stable egress IP range for allowlists. Pull request checks build runs-on: craci 1m 12s test runs-on: craci 2m 04s lint runs-on: craci 0m 31s Runs, logs and pull request checks in the usual place GitHub Actions cache as before Stable egress IP range No second pipeline to maintain Workflow files, actions and secrets stay where they are

GitHub Actions i dag

GitHub Actions er den understøttede CI-integration. Andre CI-systemer er på roadmappen. Builds kører på Linux-runnere til x86-64 og ARM64, som CRACI administrerer på europæisk bare metal-infrastruktur; Windows- og macOS-runnere er også på roadmappen.

What CRACI supports today GitHub Actions is supported today, and other CI systems, starting with GitLab CI and Jenkins, are on the roadmap. Runners are Linux on x86-64 and ARM64, managed by CRACI on European bare-metal infrastructure, with Windows and macOS on the roadmap. CI integration GitHub Actions: today GitLab CI, Jenkins: roadmap Runner operating systems Linux x86-64: today Linux ARM64: today Windows: roadmap macOS: roadmap Managed by CRACI European bare-metal infrastructure One isolated virtual machine per job Sizes from 1 to 32 vCPU, same rate on ARM64 Images: CRACI Slim, CRACI Slim ARM64, Ubuntu 24.04

Integrér compliance i dit workflow

Book en demo, og automatisér CRA-overholdelse i din CI/CD-pipeline

Book en demo