On Fri, Dec 2, 2016 at 3:22 AM Timo Rothenpieler <t...@rothenpieler.org> wrote:
> On 12/2/2016 4:14 AM, Timothy Gu wrote: > > On Thu, Dec 1, 2016 at 1:23 PM Timo Rothenpieler <t...@rothenpieler.org> > > wrote: > > > >> Travis can only run scheduled builds daily, weekly or monthly. > > > > So we run them daily, and use a bit of logic in the .travis.yml to > >> cancel out early on 3 days per week. > >> > > > > Nice! Didn't know Travis CI could do this. > > > > It needs to be explicitly requested, but I don't think that will be an > issue if we explain them our usecase: > https://docs.travis-ci.com/user/cron-jobs/ Agreed. > > > A few nits: indent the array, just as you did for `services`; the > official > > Travis CI-Coverity bridge uses COVERITY_SCAN_NOTIFICATION_EMAIL and > > COVERITY_SCAN_TOKEN, so for consistency you might want to change that. > > Updated the image to use those, updated this patch locally to do the same. > > Another thing is that currently https://github.com/BtbN/FFmpeg-Coverity > (the > > source of "ffmpeg/coverity" image) belongs to your GitHub account. Maybe > we > > should think of transferring that to github.com/FFmpeg? > > I can't create that repository myself, but so if someone could import it > from my Account, that would be nice. > That has been done my Michael as I can see. So one question: will this .travis.yml be applied to the main FFmpeg repo or the newly created FFmpeg-Coverity repo? Timothy _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
