[FFmpeg-devel] [PATCH] forgejo/workflows: add initial rudimentary CI

[Kacper Michajlow]

On Tue, 22 Jul 2025 at 00:40, Scott Theisen <scott.the.elm at gmail.com> wrote:

> On 2025/07/21 18:17, Michael Niedermayer wrote:
> > On Mon, Jul 21, 2025 at 06:37:06PM +0200, Timo Rothenpieler wrote:
> >> It runs basic fate with no special dependencies enabled on x86_64 and
> >> aarch64.
> >> ---
> >>   .forgejo/workflows/test.yml | 39 +++++++++++++++++++++++++++++++++++++
> >>   .gitignore                  |  1 +
> >>   2 files changed, 40 insertions(+)
> >>   create mode 100644 .forgejo/workflows/test.yml
> >>
> >> diff --git a/.forgejo/workflows/test.yml b/.forgejo/workflows/test.yml
> >> new file mode 100644
> >> index 0000000000..f9e032b78c
> >> --- /dev/null
> >> +++ b/.forgejo/workflows/test.yml
> >> @@ -0,0 +1,39 @@
> >> +on:
> >> +  push:
> >> +    branches:
> >> +      - master
> >> +  pull_request:
> >> +
> >> +jobs:
> >> +  run_fate:
> >> +    strategy:
> >> +      fail-fast: false
> >> +      matrix:
> >> +        runner: [linux-amd64,linux-aarch64]
> >> +    runs-on: ${{ matrix.runner }}
> >> +    steps:
> >> +      - name: Checkout
> >> +        uses: actions/checkout at v4
> >> +      - name: Configure
> >> +        run: ./configure
> > If you want to maximize coverage and maximize speed:
> > dash ./configure
> > --enable-gpl
> > (--enable-nonfree)
> > --enable-version3
> > --cc='ccache gcc' (or clang)
>
> ccache would also need a set of actions/cache steps and if the caches
> are scoped as GitHub's are, probably also another workflow to clean up
> the caches when a pull request is closed


I can help with that, I have a pretty neat setup for ccache on github.
Should be transferable here. Although I agree with Timo, ccache is a risk
if we start having some miscompilations or stale objects. It generally
works, but I wouldn't use it unless really needed. For slow/less important
configs it can be enabled, but I wouldn't enable it for all builds.

- Kacper