You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2018/04/04 14:00:05 UTC

[GitHub] wu-sheng commented on issue #1034: Collector automated testing for storage module

wu-sheng commented on issue #1034: Collector automated testing for storage module
URL: https://github.com/apache/incubator-skywalking/issues/1034#issuecomment-378609841
 
 
   > [Source code project](https://github.com/{Account ID}/{forked project name from incubator-skywalking})
   
   Forked project name is normally as same as ours. So, we can use the same name in default.
   
   > Test toolkit
   
   Test toolkit should be provided as a public image, just download and use.
   
   > Docker compose
   
   Because only two files are required, no need to create so many repositories in our org. I prefer use different folders. In pr, contributor can choose to use our provided docker-compose to test their bug-fix or feature, or they can provided one in our `docker-compose`-fork repo. 
   
   After `docker-compose` review, tested, passed, merged, the pr can be merged finally. In that cases, we have more test vessels for support different scenario.
   
   Finally, we can use some ci env to run all cases(docker-compose) for full check, before release, or test in some check point.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services