You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Mariia Mykhailova <ma...@microsoft.com> on 2016/03/02 01:20:30 UTC
Useful tips for Travis CI
Hi,
1. From https://docs.travis-ci.com/user/customizing-the-build/#Skipping-a-build
If you don't want to run a build for a particular commit, because all you are changing is the README for example, add [ci skip] to the git commit message.
(in this case we should probably remove this part from commit message during PR merge)
2. You can setup Travis builds for your fork of reef repository and run tests on branches before they become pull requests. Helpful if you don't want to run tests locally.
-Mariia
Re: Useful tips for Travis CI
Posted by Markus Weimer <ma...@weimo.de>.
Thanks!
Markus
On 2016-03-01 16:20, Mariia Mykhailova wrote:
> Hi,
>
>
> 1. From https://docs.travis-ci.com/user/customizing-the-build/#Skipping-a-build
> If you don't want to run a build for a particular commit, because all you are changing is the README for example, add [ci skip] to the git commit message.
> (in this case we should probably remove this part from commit message during PR merge)
>
>
> 2. You can setup Travis builds for your fork of reef repository and run tests on branches before they become pull requests. Helpful if you don't want to run tests locally.
>
> -Mariia
>