OSS-OO/ci-examples
OSS-OO/ci-examples
Watch
1
0
Fork
You've already forked ci-examples
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Example workflows for the free public CI at oss-oo.io — copy, push, run.
2 commits 1 branch 0 tags 4.6 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Claudiu Schuster 86f3290eb3
All checks were successful
build-artifact-free / build (push) Successful in 5s
Details Explain this check
hello / hello (push) Successful in 2s
Details Explain this check
matrix / test (3.20) (push) Successful in 2s
Details Explain this check
matrix / test (3.21) (push) Successful in 2s
Details Explain this check
rollout: install session-handoff issue template (P1.d)
2026-09-24 14:04:32 +00:00
.forgejo rollout: install session-handoff issue template (P1.d) 2026-09-24 14:04:32 +00:00
README.md ci-examples: hello, matrix, artifact-free build on oss-oo-public 2026-09-23 13:12:50 +02:00

README.md

ci-examples — free public CI at oss-oo.io

Copy-paste workflow examples for the laboratory's public CI lane. Every workflow here runs on real public runner iron — dedicated, hardened machines that exist only for community CI.

How to use it

  1. Create a repository on oss-oo.io (Actions are enabled by default).
  2. Copy one of the workflows from .forgejo/workflows/ into your own .forgejo/workflows/ directory.
  3. Push. That's it — the job picks up automatically.

The label: runs-on: oss-oo-public

Public jobs request the oss-oo-public label:

jobs:
  hello:
    runs-on: oss-oo-public

This is the only label public repositories should use. The internal oss-oo-internal lane is reserved for the laboratory's own repositories and is not reachable from outside accounts.

What you get

  • Free CI for everyone — no minutes, no billing, no signup beyond a normal oss-oo.io account.
  • One job slot — the public lane runs one job at a time; your job may queue briefly behind others.
  • Job budget: 1 GiB memory, 0.75 CPU, 20 minutes runtime, 256 processes.
  • Egress is open — your job can fetch dependencies (npm, pip, apt, crates, …).
  • Sandbox: job containers run without the docker socket, without host mounts, with a fresh ephemeral network and no-new-privileges.
  • Logs and artifacts are kept 30 / 14 days, then deleted.

What is not allowed

  • Crypto mining, hash cracking, or any sustained compute farming.
  • Spam, scraping, or attack traffic from our IP.
  • Anything illegal in the EU/Germany, or that tries to break out of the job sandbox.
  • Storing data in job workspaces (they are ephemeral and wiped).

Abuse leads to job cancellation and account termination. Reports: open an issue in this repository.

Fork pull requests

Workflows in pull requests from forks run with no repository secrets and a read-only token — reviewing a stranger's PR by running their CI is safe here.

Examples

Workflow Shows
hello.yml The smallest possible job
matrix.yml A small build matrix
build-artifact-free.yml Compile something without uploading artifacts

Questions or ideas? Open an issue — the laboratory is run by OSS-Singularity with its members.