Hello,
is there any doc presenting when Travis CI (from github) is doing the notifications? Or, maybe someone familiar with the system can provide more details.
I see it is sent for pull requests and commits to new branches. Maybe we can limit to get those notifications only for the official branches, either from some config or a filter on our email server, otherwise it may create a lot of noise.
Cheers, Daniel
On 01/05/2015 03:20 PM, Daniel-Constantin Mierla wrote:
Hello,
is there any doc presenting when Travis CI (from github) is doing the notifications? Or, maybe someone familiar with the system can provide more details.
http://docs.travis-ci.com/user/build-configuration/#Specify-branches-to-buil...
I see it is sent for pull requests and commits to new branches. Maybe we can limit to get those notifications only for the official branches, either from some config or a filter on our email server, otherwise it may create a lot of noise.
I would keep the pull-request build. That's useful, from my POW.
I can add this to the .travis.yml. In order to build only those branches:
# whitelist branches: only: - master - 4.2
In order to reduce the spam I will set the email notification to this:
on_success: never on_failure: always
Do you agree? Victor
On 05/01/15 15:30, Victor Seva wrote:
On 01/05/2015 03:20 PM, Daniel-Constantin Mierla wrote:
Hello,
is there any doc presenting when Travis CI (from github) is doing the notifications? Or, maybe someone familiar with the system can provide more details.
http://docs.travis-ci.com/user/build-configuration/#Specify-branches-to-buil...
Thanks!
I see it is sent for pull requests and commits to new branches. Maybe we can limit to get those notifications only for the official branches, either from some config or a filter on our email server, otherwise it may create a lot of noise.
I would keep the pull-request build. That's useful, from my POW.
I can add this to the .travis.yml. In order to build only those branches:
# whitelist branches: only: - master - 4.2
In order to reduce the spam I will set the email notification to this:
on_success: never on_failure: always
Do you agree?
I will add also the branch 4.1, it is officially maintained.
Building for pull requests is useful, my concern was only for notifications (not to create too much noise on mailing list with something not very useful). I think it is better to get them only on failure, when it needs an action.
Cheers, Daniel
On 05 Jan 2015, at 15:30, Victor Seva linuxmaniac@torreviejawireless.org wrote:
On 01/05/2015 03:20 PM, Daniel-Constantin Mierla wrote:
Hello,
is there any doc presenting when Travis CI (from github) is doing the notifications? Or, maybe someone familiar with the system can provide more details.
http://docs.travis-ci.com/user/build-configuration/#Specify-branches-to-buil...
I see it is sent for pull requests and commits to new branches. Maybe we can limit to get those notifications only for the official branches, either from some config or a filter on our email server, otherwise it may create a lot of noise.
I would keep the pull-request build. That's useful, from my POW.
I can add this to the .travis.yml. In order to build only those branches:
# whitelist branches: only:
- master
- 4.2
In order to reduce the spam I will set the email notification to this:
on_success: never on_failure: always
Do you agree?
Yes
/O
-
Daniel-Constantin Mierla -
Olle E. Johansson -
Victor Seva