Skip to content
Unfurl Cloud
  • Dashboard
  • Blueprints
  • Cloud
Projects Groups Topics Snippets
  • Help
  • Register
  • Sign in
  • unfurl unfurl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
Closed
Open
Issue created Mar 03, 2021 by Adam@adamOwner

support gitlab-runner as a "runtime"

Instead of running unfurl inside a python virtual machine we should add an option that runs it via gitlab runner.

It might be possible to do this out of the box: if you specify a runtime (either on the command line with --runtime or with a runtime key in contexts in unfurl.yaml) that isn't a venv: specifier it will treated as command line arguments that prepend the arguments passed to unfurl. (see _remoteCmd in __main__)

There's a simple Dockerfile for building a container with unfurl development environment but we probably want a better container for a gitlab-runner instance to use.

Assignee
Assign to
Time tracking