On Sun, Nov 27, 2016 at 1:52 PM Michael Niedermayer <mich...@niedermayer.cc> wrote:
> I dont want to give a automated travis_ci system any write or admin > access, some of what i read hinted in that direction, some of what > i read hinted that this was not needed though > giving a automated system write access would be a security issue and > we should not do that > You don't need to give Travis CI any privileges. The way it's going to work is: 1. Set up a dedicated "coverity" branch 2. Set up Travis CI to only watch changes on that branch, and when there is a new push compile the code with Coverity's custom wrappers, etc. 3. Set up a cronjob on a computer (doesn't matter who's) that pulls new commits on master into coverity every |x| days Timothy _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
