As a dev-ops engineer, I want to change the current pipeline to allow automated tests to store test results history at the test results repository for both the master and release branches.
Acceptance Criteria
The pipeline modifications should enable automated tests to store their results history.
The test results should be stored in the designated test results repository.
The changes should be implemented for both the master and release branches.
The modified pipeline should be tested and verified to ensure the test results are being stored correctly.
dotCMS Version
master
Proposed Objective
To enhance the testing process by enabling the automated tests to store their results history for better analysis and tracking.
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
User Story
As a dev-ops engineer, I want to change the current pipeline to allow automated tests to store test results history at the test results repository for both the master and release branches.
Acceptance Criteria
dotCMS Version
master
Proposed Objective
To enhance the testing process by enabling the automated tests to store their results history for better analysis and tracking.
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
_todefine
Assumptions & Initiation Needs
_todefine
Quality Assurance Notes & Workarounds
_todefine
Sub-Tasks & Estimates
_todefine