[ 
https://issues.apache.org/jira/browse/SCB-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579212#comment-16579212
 ] 

ASF GitHub Bot commented on SCB-823:
------------------------------------

coveralls commented on issue #252: [SCB-823]Fix the spring-demo image repo name.
URL: 
https://github.com/apache/incubator-servicecomb-saga/pull/252#issuecomment-412744233
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/18469584/badge)](https://coveralls.io/builds/18469584)
   
   Coverage decreased (-0.1%) to 94.199% when pulling 
**75d3ec20f7a2cc04d21888ed6e595aeb37ef381b on crystaldust:fix/image-repo-name** 
into **eac55be231aa74cb265563cb4e7ae13f8e95a689 on apache:master**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Set up a fully functional test in kubernetes environment
> --------------------------------------------------------
>
>                 Key: SCB-823
>                 URL: https://issues.apache.org/jira/browse/SCB-823
>             Project: Apache ServiceComb
>          Issue Type: Test
>          Components: Saga
>            Reporter: ZhenJu
>            Assignee: ZhenJu
>            Priority: Minor
>              Labels: kubernetes, test
>
> It would be great if we have a kubernetes test solution running the demos in 
> containers.
> With the environment, it's easier to:
>  * Scale up / down the services to test saga in different size distributed 
> systems
>  * Simulate the scenarios that different forms of errors would occur, like 
> unavailable connection, internal server error, or network delay. This could 
> be easily done by Istio



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to