The detailed description of the tasks performed by the openQA review bot is documented here
The absence of OpenQE Staging tools will shift the burden of basic validation to the QE team when the build is promoted to TEST, too late to catch and fix them without delays
Currently without the OpenQA Staging feature, the Release Team is unable to verify the baseline quality of builds before they are handed over to QA. Due to the absence of this early detection step, basic integration issues are only being identified during the build testing phase, delaying the discovery of the bugs.
Impact on SLES 16.1 project:
-
Inefficiency: Finding basic bugs at the end of the cycle forces us to restart the entire product build, including approvals cycle, and deployment process for simple fixes. This is a costly and unplanned use of engineering and QA time
-
Schedule Delays: These repetitive cycles are significantly increasing our testing turnaround time. This inefficiency has a high potential to directly impact our ability to meet upcoming Milestone dates, causing significant project delays.
Reference: Originally tracked as GITW-32.
Task Scope This task focuses specifically on the Build Phase.
- Configure the pipeline to build the necessary artifacts (repositories/ISOs/Images) required for testing.
- Deliverable: Valid build artifacts ready for consumption by the openQA bot.
The detailed description of the tasks performed by the openQA review bot is documented here
The absence of OpenQE Staging tools will shift the burden of basic validation to the QE team when the build is promoted to TEST, too late to catch and fix them without delays
Currently without the OpenQA Staging feature, the Release Team is unable to verify the baseline quality of builds before they are handed over to QA. Due to the absence of this early detection step, basic integration issues are only being identified during the build testing phase, delaying the discovery of the bugs.
Impact on SLES 16.1 project:
Inefficiency: Finding basic bugs at the end of the cycle forces us to restart the entire product build, including approvals cycle, and deployment process for simple fixes. This is a costly and unplanned use of engineering and QA time
Schedule Delays: These repetitive cycles are significantly increasing our testing turnaround time. This inefficiency has a high potential to directly impact our ability to meet upcoming Milestone dates, causing significant project delays.
Reference: Originally tracked as GITW-32.
Task Scope This task focuses specifically on the Build Phase.