Skip to content
Snippets Groups Projects
Select Git revision
  • 673-add-devblog-pages
  • master default protected
  • update-onboarding
  • increase-burst-on-archmanweb
  • add-aurweb-tracing
  • block-uptime-robots
  • enable-gitlab-spamcheck
  • dbscripts-git-repo
  • artifact-signing-rfc
  • mysql_dashboard
  • upgrade_docs
  • aur_robots.txt
  • mariadb-nocow
13 results
Blame Permalink
  • Kristian Klausen's avatar
    06e02527
    gitlab_runner: Add VM based executor (libvirt-executor) · 06e02527
    Kristian Klausen authored 
    For some workloads running in a container is too restrictive, ex:
arch-boxes (loop device, filesystem mount, pacstrap) and archiso
(pacstrap). Currently they both run a TCG accelerated QEMU VM, which is
very slow and painful to work with. We should provide a better option to
our users!

This adds a hardware accelerated VM for this kinds of workloads, which
is way faster and you can do whatever you like (mostly)!

Fix #283
    Verified
    06e02527
    History
    gitlab_runner: Add VM based executor (libvirt-executor)
    Kristian Klausen authored 
    For some workloads running in a container is too restrictive, ex:
arch-boxes (loop device, filesystem mount, pacstrap) and archiso
(pacstrap). Currently they both run a TCG accelerated QEMU VM, which is
very slow and painful to work with. We should provide a better option to
our users!

This adds a hardware accelerated VM for this kinds of workloads, which
is way faster and you can do whatever you like (mostly)!

Fix #283
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
vault_gitlab_runner.yml 743 B