[FFmpeg-devel] autofate system

[Andriy Gelman]

Hi,

On Tue, 06. Oct 14:16, Chris Miceli wrote:
> Hi all,
> 
> I have written a small system called autofate (
> https://github.com/cmiceli/autofate) which is designed to basically run
> fate on every commit in master, ideally capturing and then reporting broken
> builds. It's written in rust so that it can run on a wide variety of
> platforms (I am currently testing on multiple architectures and multiple
> operating systems).
> 
> Ideally, I'd love to get this reporting to the fate server and get other's
> running on various flavours of hardware where ffmpeg support is used
> widely. Right now I have it on 64bit and 32 bit rpi for example.
> 
> What I was wondering is:
>  1. Do people think this is a step in the right direction?
>  2. How would we like to integrate with FATE server?
>  3. How would we like this to report failures? Email?
>  4. Any other features desired, I'm happy to add or accept pull requests.
> 
> I look forward to hearing thoughts from the community, have a great day.
> 

I'm not familiar with the setup on fate.ffmpeg.org, but we have something
similar running patchwork.ffmpeg.org 

The site fetches patches from the mailing list. Jenkins server runs make/fate
and reports the results back to patchwork. 

Patchwork itself is an open source project:
https://github.com/getpatchwork/patchwork
https://github.com/michaelni/patchwork-update-bot

Slides to setup the CI in Jenkins:
https://speakerdeck.com/stephenfin/mailing-list-meet-ci

There are some problems with patchwork when a user sends a new version, but does
not send the full series. These patches are not linked and not captured
by CI. It would be great to fix this eventually..

Something else to keep in mind: There are often discussions to switch to gitlab
or something similar. And they will probably come up again. 

Thanks,
-- 
Andriy