, will produce
> > too
> > > > many log, that will treat Travis log size limit.
> > > >
> > > > 2018-07-10 19:23 GMT+08:00 Sure :
> > > >
> > > > > Agree!
> > > > >
> > > > >
> > > > > 1. Just like
gt; > >
> > > >
> > > > 1. Just like willem.jiang said, we can push multiple SC versions to
> > > docker
> > > > hub
> > > > 2. Chassis integration test can run with different SC version in
> every
> > > time
> > > >
&
run with different SC version in every
> > time
> > >
> > >
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "willem.jiang";
> > > 发送时间: 2018年7月10日(星期二) 下午5:16
> > > 收件人: "dev";
> > >
---------
> > 发件人: "willem.jiang";
> > 发送时间: 2018年7月10日(星期二) 下午5:16
> > 收件人: "dev";
> >
> > 主题: Re: [DISCUSS] about integration test
> >
> >
> >
> > Current ServiceComb CI just leverage service of Travis[1] which has a
> v
ng";
> 发送时间: 2018年7月10日(星期二) 下午5:16
> 收件人: "dev";
>
> 主题: Re: [DISCUSS] about integration test
>
>
>
> Current ServiceComb CI just leverage service of Travis[1] which has a very
> good integration with Github.
>
> Current we don't test the multiple SC at s
: "dev";
: Re: [DISCUSS] about integration test
Current ServiceComb CI just leverage service of Travis[1] which has a very
good integration with Github.
Current we don't test the multiple SC at same time, but I think with the
help of docker, it could easy for us to run the examp
ServiceComb is an open source project that has been adopted for a variety
of commercial scenarios. As wrote in the report, at least more than 10
users have used ServiceComb for commercial use.
Therefore, our integration testing will be more and more comprehensive and
huge, it is a good idea to
currently we embed integration test with PR CI
but:
1.we will add more and more integration test case
2.test time will be more and more longer
3.integration test should include work with multiple SC versions
4...
so, maybe it's better that make integration test to be a independent
project,
