Swapnil, What is the significance of the Travis results? I see that the Travis job failed on your PR #107, which was a doc change and therefore of particular interest to me. There's nothing wrong with your change and it certainly didn't introduce new code of any kind. What do we learn from Travis in this case? Will this be a typical result for all doc submissions?
On Thu, Feb 25, 2016 at 5:10 PM, Swapnil Bawaskar <[email protected]> wrote: > Do we want build emails from travis sent to the dev list? > > The default mechanism from the travis site > <https://docs.travis-ci.com/user/notifications/> is as follows: > > By default, a build email is sent to the committer and the author, but only > if they have access to the repository the commit was pushed to. This > prevents forks active on Travis CI from notifying the upstream repository’s > owners when they’re pushing any upstream changes to their fork. It also > prevents build notifications from going to folks not registered on Travis > CI. > > The email address is then determined based on the email address in the > commit, but only if it matches one of the email addresses in our database. > We synchronize all your email addresses from GitHub, solely for the purpose > of build notifications. > > > We can configure travis to send emails to the dev list when the state of > the build changes (from passing to failing OR from failing to passing). No > multiple emails on failing builds. > > Thanks! > Swapnil. >
