Closed phlogistonjohn closed 2 years ago
We discussed this a bit in a call earlier today. The current plan is to investigate the use of centos ci for this:
After the above, the remaining work would be like what we currently have in the github actions with a few tweaks (probably).
The initial project setup work with be handled by @anoopcs9 with my help.
Request for Samba project namespace: https://pagure.io/centos-infra/issue/537
After fighting with various issues we are now ready on our dedicated Samba Namespace. Jobs and other scripts are currently residing under my GitHub username in samba-centosci repository. I have also setup GitHub workflows to verify/update jobs as and when they are modified in the repository.
Currently looking into a frequent
minikube
start failure on CentOS installed host.
This is now being fixed with https://github.com/kubernetes/minikube/pull/13482. Next step is to establish an internal CI registry for Samba project namespace to be used as local mirror.
Updates:
CI jobs are setup to be run against each PR. Additionally they are triggered as nightly jobs.
In the light of discussions around the need for running tests with 3 different Kubernetes versions, decision has been made to only run centos-ci/sink-clustered/mini-k8s-1.23 against each PR to samba-operator repository. No change in nightly configured jobs.
Currently the tests for clustered SmbShares are not run in the CI. This is because the CI uses a single node k8s cluster with no ability to provision RWX PVCs.
At the bare minimum the test cluster must support Read-Write-Many. Ideally it would also support >=3 k8s nodes.
I don't know if the github CI is sufficient for this.