rohityadavcloud opened a new issue, #7010: URL: https://github.com/apache/cloudstack/issues/7010
Followup from https://github.com/apache/cloudstack/pull/6956 Suggestions, optimisations to consider and implement: - Reduce no. of jobs, for ex. run more component tests in a group (as github actions timeout is 6hrs), overall less runners - Check for PR diff/changes and only run component tests if required (for example when java changes, or run tests by changes type) - Run/skip UI tests if not UI change; or only run UI tests if UI changes only - Explore pipeline and artifact upload/download, passing across jobs Example pipeline can be: Check type of changes, do we need to build UI or java code -> Do mvn -Dnoredist -Dsimulator build with unit tests -> if it passes -> run smoketests (2-4 runners) and integration tests (2-4 runners) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
