[
https://issues.jboss.org/browse/SWSQE-450?page=com.atlassian.jira.plugin....
]
Filip Brychta commented on SWSQE-450:
-------------------------------------
Here is first obvious problem - right now we have 3 triggers which are starting
Istio-and-Kiali-on-Openshift job. First is nightly timer, kiali-core-pr-e2e-test and
kiali-ui-pr-e2e-test. Istio-and-Kiali-on-Openshift job is not allowed to be run in
parallel so when the job is in progress other runs have to wait.
Analyze Pipeline Execution Times
--------------------------------
Key: SWSQE-450
URL:
https://issues.jboss.org/browse/SWSQE-450
Project: Kiali QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Filip Brychta
Priority: Minor
PR Jenkins CI jobs are taking at times 30 min to complete. Are there any optimization
opportunities that could improve on the pipeline execution time duration?
This is just *one* snapshot of a pipeline time breakdown, but perhaps s
17 minutes was waiting (Spin up the Jenkins Agent)
17 minutes running the jobs themselves
Almost 2 minutes (1.30 min) to Install Istio (Which doesn't sound too much)
3 Minutes to Install Bookinfo
8 minutes to Build and Deploy Kiali
4 minutes -> to deploy kiali with Kiali Checker
4 minutes -> to build with Yarn
2 Minutes to run e2e-tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)