Deng Xiaodong thanks for helping us with this. I hope this will help us in developing and testing fast. I would like to ask is there a provision to cancel our own builds in travis. I can see sometimes contributors are pushing multiple commits in small intervals of time leading to multiple builds. If we can kill/cancel old builds and let only the latest build run it would be better use of resources.
On Wed, 21 Nov 2018 at 21:56, Deng Xiaodong <xd.den...@gmail.com> wrote: > Hi folks, > > I noticed that testing is somehow a problem for some folks who would like > to contribute (either have trouble setting local testing env, or misused > Pull Request to test). Actually because Airflow is using Travis CI for unit > testing, running testing for any of your change/commit is very very easy. > > ****Steps**** > 1. Go to https://travis-ci.org/, click “Sign in with GitHub”. If you > haven’t done this before, possibly it will ask you to “Authorize Travis CI > for Open Source”. > 2. After this is done, you may be redirected to > https://travis-ci.org/account/repositories. Then you will see a list of > your public repositories. Let’s assume you have already forked Airflow, > then just toggle it on. > 3. Everything is good to go! From now on, if you make any change/commit to > your own fork of Airflow, the Travis CI test will be triggered > (Travis-related files is already included in the Airflow codebase). > > ****Why to do this**** > - You don’t have to set up local testing env, or misuse Pull Request to > test your code change. > - Travis CI is free for Open Source project (public repo), but it only > allows 5 concurrent tests. On the other hand, Apache is using > paid-subscription (possibly for unlimited concurrent tests). So mis-using > Pull Requests to test your change/commit will result in a slightly bigger > bill that ASF receives. > > Hope this is somehow helpful for folks who would like to contribute. > > XD > -- Sai Phanindhra, Ph: +91 9043258999
