schurzi 9b32aca0ca run our CI tests periodically (#634) ... * allow multiple instances for os vm tests Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * add scheduled trigger to all test actions Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * use different scenario names Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * use different scenario names Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * use different scenario names Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * use username to create uniqe vms Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * use compatible name Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> * add explaination Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com> --------- Signed-off-by: Martin Schurz <Martin.Schurz@t-systems.com>		2023-02-07 09:27:46 +01:00
..
prepare_tasks	add testing of os_hardning on vm	2022-07-09 00:52:58 +02:00
verify_tasks	add testing of os_hardning on vm	2022-07-09 00:52:58 +02:00
converge.yml	reduce testing on vm	2022-07-11 16:08:35 +02:00
INSTALL.rst	add testing of os_hardning on vm	2022-07-09 00:52:58 +02:00
molecule.yml	run our CI tests periodically (#634)	2023-02-07 09:27:46 +01:00
prepare.yml	use correct centos stream images, try to fix prepare step for debian tests	2022-10-25 18:59:11 +02:00
requirements.yml	add testing of os_hardning on vm	2022-07-09 00:52:58 +02:00
verify.yml	reduce testing on vm	2022-07-11 16:08:35 +02:00