[
https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin....
]
Matt Mahoney commented on SWSQE-145:
------------------------------------
There will be, and are now, test cases that depend on traffic being generating while the
test is running.
For example, Service Graph & Json test cases will validate Edge color, Traffic
throughput, Error rates, etc. If the traffic stopped prior to running the tests, then the
expected throughput/Error-rates/Edge-colors may not be as expected, and thus potentially
causing false failures.
Modurlarizing the pipeline allows us much flexibility on how we want to build the needed
scenarios, perhaps we need to consider a bit more about how we will build those scenarios
(i.e. various Jenkins pipeline jobs for needed scenarios or one master pipeline job with
tunable parameters for controlling traffic/mesh-deployments/suites-to-be-run/etc or a
combination thereof)?
Modularize CI/CD Pipline
------------------------
Key: SWSQE-145
URL:
https://issues.jboss.org/browse/SWSQE-145
Project: Kiali QE
Issue Type: Epic
Reporter: Matt Mahoney
Assignee: Guilherme Baufaker RĂªgo
Attachments: Kiali Pipeline Proposal.png
The CI/CD pipeline has become more complex and challenging with which to build CI/CD
usage-cases and to add new functionality:
Use Case Examples:
1) Deploy Istio -> Deploy&build-kiali -> Deploy All Service Meshes ->
Deploy Traffic Generator on all Service Meshes -> Run all test suites
2) Deploy built Kiali -> Run REST suite
3) Build and Deploy Kiali -> Run all test suites
4) Run UI suite on any Openshift Cluster
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)