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

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

  • Comments

    Be the first to comment!

    Similar Projects

    This project is one of its kind!