Il giorno lun 26 giu 2023 alle ore 19:10 Stefan Kalscheuer via openwrt-devel <[email protected]> ha scritto: > > The sender domain has a DMARC Reject/Quarantine policy which disallows > sending mailing list messages using the original "From" header. > > To mitigate this problem, the original message has been wrapped > automatically by the mailing list software. > > > ---------- Forwarded message ---------- > From: Stefan Kalscheuer <[email protected]> > To: [email protected] > Cc: > Bcc: > Date: Mon, 26 Jun 2023 19:07:25 +0200 > Subject: GitHub Actions usage on OpenWRT/LEDE main/master > Hi all, > > I don't know if that topic ever came up yet, but I stumbled across it > recently. > > TL;DR: > > Is there really a point in running GH actions 4 times on both main and > master branch and both OpenWRT and LEDE org repositories or should we > consider being little more economic with the resources, e.g. by > disabling the actions on the mirror and/or the master branch? > > > Little more background: > > The default branch was renamed from "master" to "main" with a sync to > "master" for backwards compatibility. The git repo is mirrored to GitHub > in the OpenWRT org ( https://github.com/openwrt/openwrt ) and also to > the LEDE org ( https://github.com/lede-project/source ). > > Then we have quite elaborate CI workflows using GitHub Actions which can > trigger up to ~450 jobs (~200 build jobs plus setup/caching stuff) which > take around 2 hours to complete (e.g. on current top commit 539cb53). > That's totally reasonable considering the impact of the changes made. > There are smaller changes that might just trigger 10 and run 5min. > > Every aspect of this probably fine for itself, but when it all comes > together... > The GH actions are triggered in all repos named on all branches, so we > trigger all this at least 4 times (actually just ~3 times, as most > pipelines are failing on the LEDE mirror) >
master is already excluded and ignored. Totally unaware LEDE mirror has actions enabled... For me that should be just disabled and the entire thing is archived. But I don't have access to that. > I don't see a real benefit running all this stuff 4 times. Beside the > eco aspect, that simply utilizes quite a few runners, so a new/updated > PR sometimes takes an hour before the tasks get picked up and start running. > Can we list the 4 times? - Currently it's on openwrt one per pr and when a push is done. - Also in LEDE mirror, it's again one So it's 2 that should be reduced to 1. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
