[FFmpeg-devel] [PATCH] travis: setup for automated coverity builds
timothygu99 at gmail.com
Fri Dec 2 19:36:42 EET 2016
On Fri, Dec 2, 2016 at 3:22 AM Timo Rothenpieler <timo at rothenpieler.org>
> On 12/2/2016 4:14 AM, Timothy Gu wrote:
> > On Thu, Dec 1, 2016 at 1:23 PM Timo Rothenpieler <timo at 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:
> > A few nits: indent the array, just as you did for `services`; the
> > 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
> > source of "ffmpeg/coverity" image) belongs to your GitHub account. Maybe
> > 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?
More information about the ffmpeg-devel