Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gnome-build-meta gnome-build-meta
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 126
    • Issues 126
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-build-metagnome-build-meta
  • Issues
  • #206
Closed
Open
Issue created Sep 17, 2019 by Javier Jardón@jjardonMaintainer

Test OS and apps keep working in the VM image

We currently build a GNOME VM as part of our default pipeline

I see two levels of testing:

  1. UI testing, that can be potentially be done in a VM 1.1 Seems http://open.qa/ could be a good option for this
  2. Deploy and test the image in real hardware, and then test things keep working there 1.2 Related projects about this: https://www.lavasoftware.org/ (https://kernelci.org/)

Ideally we would like to run those test for each MR, and gate the change if something fails

Edited Apr 29, 2020 by Javier Jardón
Assignee
Assign to
Time tracking