Playwright on GitHub Actions: The setup that actually runs fast
https://endform.dev/blog/playwright-github-actions
This piece walks through that setup end to end. By the end you will know where your time is going, have a workflow that gives useful feedback on every PR, and know the point at which sharding actually becomes worth it.
Self-hosted Forgejo Actions Runner – David Bushell – Web Dev (UK)
https://dbushell.com/2025/08/15/self-hosted-forgejo-actions-runner/
Did I mention GitHub is dead to me? I’m moving my code to a self-hosted Forgejo instance at git.dbushell.com. Today I added Actions.
Forgejo Actions are a thing like GitHub Actions for “continuous integration”. Love a bit of CI! Forgejo Actions don’t work out of the box. You need to provide a “runner” which is a machine where all the action happens inside a containerised environment.
Farewell to Tinderbox, the world’s 1st? 2nd? Continuous Integration server
http://oduinn.com/blog/2014/06/04/farewell-to-tinderbox/
In April 1997, Netscape ReleaseEngineers wrote, and started running, the world’s first? second? continuous integration server. Now, just over 17 years later, in May 2014, the tinderbox server was finally turned off. Permanently.
Farewell to Tinderbox, the world’s 1st? 2nd? Continuous Integration server
http://oduinn.com/blog/2014/06/04/farewell-to-tinderbox
In April 1997, Netscape ReleaseEngineers wrote, and started running, the world’s first? second? continuous integration server. Now, just over 17 years later, in May 2014, the tinderbox server was finally turned off. Permanently.