Actually, I never the number of Travis concurrent build in Weex is larger than
1, however, I do notice the maximum concurrent jobs in one build is five [1].
Anyway, I think we have no choice but live with limited Travis CI resource we
have.
[1]
https://docs.travis-ci.com/user/for-beginners/#bu
1. All projects using Travis share the same pool of resources.
2. The ASF pays Travis for ~40 builders. each project is limited to no more
than 5 concurrent builds.
links：
1. https://issues.apache.org/jira/browse/INFRA-18862
2. https://issues.apache.org/jira/browse/INFRA-18892
York Shen 于2
Any information you can share with us?
> 在 2019年8月8日，19:11，王仁敏 写道：
>
> Thanks for both of you.
>
> in Weex, we have tried to use Travis CI resources as less as possible. in
> Weex the Travis CI job will early stop if it don't need to run continue.
> for example, if there are not android file
Status check to pass before merge is enabled now.
> 在 2019年8月8日，19:11，王仁敏 写道：
>
> Thanks for both of you.
>
> in Weex, we have tried to use Travis CI resources as less as possible. in
> Weex the Travis CI job will early stop if it don't need to run continue.
> for example, if there are not an
Thanks for both of you.
in Weex, we have tried to use Travis CI resources as less as possible. in
Weex the Travis CI job will early stop if it don't need to run continue.
for example, if there are not android file changed, the android lint check
job and android check job will stop once it enter
I totally agreed your first point and I shall create a JIRA ticket to INFRA
to let it happen.
As for your second point, I found a JIRA issue about this. I am pretty Weex
doesn’t use Travis resource as Apache Flink did [1]. (No offense)
Our rough metrics shows that Flink used over 5800 hours of bu
Unfortunately there is no way to fix your second point when working in
the apache/* repositories as far as I know.
This is the account of Apache Software Foundation, which is shared
between all projects.
If you fork the repo and work in your own namespace, you can use your
own Travis account and ha
Those day I spend some time updating Travis CI of incubator-weex, during
the development process, I found some problems and the below is my
suggestion,
# FIrst I recommend prohibiting merging the PR that Travis CI builds failed
Travis CI build failed means that there is something wrong. If we for
