Project Description

Our current workflow for contributing to compliance as code requires manual testing. Automated testing either through the upstream CI or openQA would lower development time.

Goal for this Hackweek

  • Working prototype for OpenQA testing (hard, but openQA is awesome) OR
  • Testing for SLES on the upstream CI (probably easier, but needs cooperation from upstream)

Resources

Compliance as Code - Upstream

Documentation for openQA

Looking for hackers with the skills:

openqa complianceascode github-ci

This project is part of:

Hack Week 22

Activity

  • over 1 year ago: c-hagenest left this project.
  • over 1 year ago: okurz liked this project.
  • over 1 year ago: abergmann liked this project.
  • over 1 year ago: idefx disliked this project.
  • over 1 year ago: idefx liked this project.
  • over 1 year ago: robert.richardson liked this project.
  • over 1 year ago: tschmitz liked this project.
  • over 1 year ago: cdywan liked this project.
  • over 1 year ago: c-hagenest started this project.
  • over 1 year ago: c-hagenest added keyword "complianceascode" to this project.
  • over 1 year ago: c-hagenest added keyword "github-ci" to this project.
  • over 1 year ago: c-hagenest added keyword "openqa" to this project.
  • over 1 year ago: c-hagenest originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    QJobViewer by apappas

    [comment]: # (Please use the project descriptio...


    Test Results for openQA on GitHub by livdywan

    Project Description

    Jobs in openQA are us...