Introduce api tooling for Jenkin e2e spec
What does this MR do and why?
This MR introduces new api tooling and an updated docker image to arrange the preconditions for the Jenkins e2e spec
This is done to make the spec more robust and take it out of quarantine.
Related issues:
The tooling is introduced monorepo style.
Edit: monorepo style doesn't work with the way the QA docker image is built.
It is updated to fit into QA::Vendor and flattened in order to be picked up by the file loader.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Sean Gregory