We have added the the getting started scripts a while ago and they are already conceptualized as tests. The return 0 if they worked, or any other return code if they failed. We would like to run them in Jenkins before every release, to save us time in the release process. Currently, the tests have to be run manually with is time consuming and error prone.
Testing should be possible for nightly as well as release branches
Implementation
Operators
In the operator, every test script should have a name conforming to test_*.sh. (i'd say the script cannot make any assumptions about where it is running)
Jenkins
Most of the work will need to be done on the Jenkins side. Jenkins should:
- Look for all the
test_*.sh scripts in the repo
- start a cluster for each one. No operators need to be installed
- run the script and capture the output
We would add another "Tab" in jenkins (like nightly, custom, etc.) for the docs tests.
Steps
As usual, we'll
Acceptance criteria
Tests working
Not all tests are working right now, but the basic infrastructure is in place. I made tickets for the tests that do not work:
Follow-Up tickets
We have added the the getting started scripts a while ago and they are already conceptualized as tests. The return
0if they worked, or any other return code if they failed. We would like to run them in Jenkins before every release, to save us time in the release process. Currently, the tests have to be run manually with is time consuming and error prone.Testing should be possible for nightly as well as release branches
Implementation
Operators
In the operator, every test script should have a name conforming to
test_*.sh. (i'd say the script cannot make any assumptions about where it is running)Jenkins
Most of the work will need to be done on the Jenkins side. Jenkins should:
test_*.shscripts in the repoWe would add another "Tab" in jenkins (like nightly, custom, etc.) for the docs tests.
Steps
As usual, we'll
test_*.shscripts (done:spike/docs-testing)Acceptance criteria
Tests working
Main docs CI docs testing documentation#367Not all tests are working right now, but the basic infrastructure is in place. I made tickets for the tests that do not work:
Follow-Up tickets