Agree with your idea
-- --
??: "Zen Lin";
: 2018??7??9??(??) 4:05
??: "dev";
: [DISCUSS] Detail design for linking servicecomb-java-chassis-doc tousers
of website.
As Liubao have renew a user docs in
I think we may change the travis script a little bit, to find out if we can
run the integration test once per day.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Jul 11, 2018 at 12:45 AM, wjm wjm wrote:
> multiple SC is no problem, infact, not all test case should be run for
>
multiple SC is no problem, infact, not all test case should be run for
multiple SC
the problem is Travis is so slow
yes, we can not ask too much about that, so my suggestion is to make
integration test independent
that will not block our PR
and integration test run once a day at least, can make
As Travis is a free service for Open Source projects, we cannot ask too
much about that.
Current ASF provides Jenkins Service here[1], there are some shortcoming
if we use it, such as lots of projects use it, and it doesn't integrate
with github.
For running the test case with different SC, I
yes
everything no problem. but:
1.Travis is so slow, not our integration test too slow
when run in our development environment, it's very fast.
2.when run all test case multi times with different SC, will produce too
many log, that will treat Travis log size limit.
2018-07-10 19:23 GMT+08:00
Agree!
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
-- --
??: "willem.jiang";
: 2018??7??10??(??) 5:16
??: "dev";
That could be great. Well there is an issue [1] to discuss about how
different LRA implementations can register participants with each other.
[1] https://github.com/eclipse/microprofile-lra/issues/17
2018-07-09 19:50 GMT+08:00 Willem Jiang :
> Hi Feng,
>
> Thanks for the information. It's could
