4 ms·

Couldn't they (or someone) set up a Github Action to compile the project on every release?

• heavyset_go 5y ago
  GitHub Actions free tier comes with ~34 hours of free compute time with 500MB storage. Pro comes with 50 hours and 1GB. Enterprise comes with much more. Building on Windows or macOS divides those compute rates by 2 and 10 respectively. For a project with frequent point releases, building Chromium via GitHub might require a monetary commitment.
  • nicce 5y ago
    Has it changed? It used to be unlimited for open projects.
    • heavyset_go 5y ago
      I wasn't aware it was ever free for open projects. Reading this page shows that you're right[1], public repositories can use GitHub Actions for free. [1] https://github.com/features/actions https://github.com/features/actions
      • moffkalast 5y ago
        So what's stopping them?
        • heavyset_go 5y ago
          Seems like something someone with some time can make a pull request for ;)
• easton 5y ago
  I forked the repo with the intention of doing this a couple months ago. The default Windows runner for Actions doesn’t have enough free disk space to compile Chromium (at least, given the build instructions the project provided). Given it took an hour to fail every time, it made trying to optimize hard and I eventually gave up.
  • francisduvivier 5y ago
    Got a link to that fork? I might want to pick that up sometime.
    • easton 5y ago
      https://github.com/jedieaston/ungoogled-chromium-windows https://github.com/jedieaston/ungoogled-chromium-windows isn't my original attempt (I deleted the original repo, oops), but I recreated pretty much where I was. GH Actions runners only have 14GB of usable space, and Chromium requires 100GB or so of free space to compile on Windows apparently: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/windows_build_instructions.md#system-requirements https://chromium.googlesource.com/chromium/src/+/refs/heads/...