-
Epic
-
Resolution: Done
-
Critical
-
None
-
[plugin][openshift-tests] Review plugin architecture
-
False
-
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
OpenShift SPLAT - Sprint 256, OpenShift SPLAT - Sprint 257, OpenShift SPLAT - Sprint 258, OpenShift SPLAT - Sprint 259, OpenShift SPLAT - Sprint 260, OpenShift SPLAT - Sprint 261
Goal:
- Review the plugin architecture offloading capabilities of plugin to Golang code, preventing complex operations like parallel execution, blocker plugin, etc in shell script, and unblocking the developer to add more features to the plugin if it is required
- Review existing failures caused by the plugin environment, which runs openshift-tests in a custom container image, instead of payload-provided image. Ideally the openshift-tests should run inside it's own image to prevent missing dependencies in the future.
Why:
The openshift-tests-plugin is the core responsible to execute the steps for the conformance workflow. The plugin capabilities grew a lot, following it's complexity, making the maintenance and troubleshooting, alongside limiting to make more complex operations as it was written in shell script.
The test is also another challenge which makes the bash script a complex structure depending of the environment.
The proposal is to offload from shell script the most complex operations, mostly all is possible, writing in Golang which is a common language used by the team, aiming to increase the confidence in the code allowing the possibilities to create test scenarios, alongside expanding the developer the possibility to test locally.