From: Scott Theisen <scott.the.elm@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] forgejo/workflows: add initial rudimentary CI Date: Mon, 21 Jul 2025 18:40:12 -0400 Message-ID: <d0ee0bad-1606-4e67-81a9-6a1bd160bf32@gmail.com> (raw) In-Reply-To: <20250721221735.GB29660@pb2> 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@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. > --assert-level=2 > --tempprefix=somebasepaththatcanbeusedforcreatingtemporaryfiles > --enable-whatever-is-insalled > > no more comments from me, patch can be applied once everyone is happy > > thx > > [...] > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-21 22:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-21 16:37 Timo Rothenpieler 2025-07-21 17:02 ` Leo Izen 2025-07-21 17:44 ` Timo Rothenpieler 2025-07-21 19:24 ` Timo Rothenpieler 2025-07-21 22:17 ` Michael Niedermayer 2025-07-21 22:40 ` Scott Theisen [this message] 2025-07-21 23:27 ` Kacper Michajlow 2025-07-21 23:00 ` Timo Rothenpieler
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=d0ee0bad-1606-4e67-81a9-6a1bd160bf32@gmail.com \ --to=scott.the.elm@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git