-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
konflux migration / E2E
-
Quality / Stability / Reliability
-
False
-
-
False
-
To Do
-
100% To Do, 0% In Progress, 0% Done
move E2E tests into konflux.
we have to separate test suites; one in jenkins (runs daily), and another in repo workflows (runs upon PR events or merges to trunk).
for jenkins jobs, as a first phase, we can trigger them from a konflux test-integration.
later we can migrate the job entirely to run from within konflux.
GH actions will have to migrate entirely.
here are some details provided by the konflux users help forum:
generally:
- the basic integration-test 'enterprise-contract' was a required part of the initial migration (as described in the console-dot guide)
- migrating any other (custom) integration-tests depended on whether their system is considered legacy or not:
- tests in github actions, like our PR/push E2E suites, can remain as-is, but are recommended to migrate at some point
- tests in jenkins jobs, like our daily E2E smoke-tests, can be considered legacy and as such were advised to migrate ASAP (but were still not blocking for initial migration)
- whether a system is considered "legacy" should be verified with the specific system owner (in our case i think app-interface own the jenkins instances we're using, so we should contact them to get a definite answer)
specifically for our jenkins daily smoke-tests suite:
- migrating any build jobs used by tests was mandatory for initial migration (like cypress container image builds – see OCMUI-2312)
- migrating test execution was not strictly mandatory, but recommended, to benefit from release gating and better performance (hence this epic was opened and split from the main epic – OCMUI-2236)
- migrating the trigger was mandatory – i.e. even in the case of running our suite from within a jenkins job and not a konflux test scenario, we needed to move to using a konflux integration-test to call the jenkins job