run our CI tests periodically (#634)
* allow multiple instances for os vm tests Signed-off-by: Martin Schurz <[email protected]> * add scheduled trigger to all test actions Signed-off-by: Martin Schurz <[email protected]> * use different scenario names Signed-off-by: Martin Schurz <[email protected]> * use different scenario names Signed-off-by: Martin Schurz <[email protected]> * use different scenario names Signed-off-by: Martin Schurz <[email protected]> * use username to create uniqe vms Signed-off-by: Martin Schurz <[email protected]> * use compatible name Signed-off-by: Martin Schurz <[email protected]> * add explaination Signed-off-by: Martin Schurz <[email protected]> --------- Signed-off-by: Martin Schurz <[email protected]>
This commit is contained in:
1 parent
8d667aa069
commit
9b32aca0ca
7 files changed
+16
-1
No files matched your search
@@ -8,7 +8,10 @@ driver:
|
||||
provider:
|
||||
name: libvirt
|
||||
platforms:
|
||||
- name: instance
|
||||
# we need to name every instance differntly to start multiple VMs on the same host (parallelization)
|
||||
# since we also need to use different OS users to run the tests because of how molecule operates,
|
||||
# the VM names must be predictable by OS user (to clean up canceled runs)
|
||||
- name: "${USER}"
|
||||
box: "generic/${MOLECULE_DISTRO}"
|
||||
memory: 1024
|
||||
cpus: 2
|
||||
|
||||
Reference in new issue
Block a user