Am 11.08.23 um 17:12 schrieb Gert Doering:
Hi,
generally good, but...
On Fri, Jul 28, 2023 at 02:40:05PM +0200, Frank Lichtenheld wrote:
index 00000000..0620f638
--- /dev/null
+++ b/.github/workflows/coverity-scan.yml
@@ -0,0 +1,45 @@
+name: coverity-scan
+on:
+ schedule:
+ - cron: '0 20 * * *' # Daily at 20:00 UTC
+ workflow_dispatch:
... not sure this is the best way to approach the run limit, as
we can have many days with no commits at all, so we'd waste credits.
Maybe cache the last commit ID and only run coverity if this has
changed? Or run it "on commit", but cache the current day, and only
run it again on the next commit that's not on the same day?
(My typical workflow is "you folks queue up patches, and then I find
half a day of free time, and go merge&push as many as I can make sense of")
You can get that behaviour but it is tricky. You have to resort tricks
like this: https://github.com/orgs/community/discussions/26519 of saving
something to a cache and then reading the cache on the next run and
check if something changed. We can probably implement like that and then
trigger on push too?
Arne
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
