Go to file
github-actions[bot] 6c2d68b946 flake.lock: Update
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:Nixos/nixpkgs/ef355dde3c80e7ee30aa65aa5bf76e0b1b00bcc2' (2023-11-18)
  → 'github:Nixos/nixpkgs/ae03901e1aa89caad3e04a883ebf39cc7caeb472' (2023-11-20)
2023-11-20 08:39:53 +00:00
.github add dependabot && flake update 2023-10-27 08:34:04 +02:00
buildbot_nix fix status_name and virtual_builder_name 2023-11-20 09:07:45 +01:00
examples make evalWorkerCount configurable 2023-11-12 07:23:35 +01:00
nix switch to ensureDBOwnership for buildbot 2023-11-18 09:17:52 +01:00
.gitignore also create webhooks automatically 2023-10-12 17:50:43 +02:00
.mergify.yml add mergify 2023-10-12 23:59:45 +02:00
default.nix add buildbot_nix as a python package to buildbot 2023-10-31 11:35:35 +01:00
flake.lock flake.lock: Update 2023-11-20 08:39:53 +00:00
flake.nix switch to nixpkgs master 2023-11-18 09:17:52 +01:00
pyproject.toml add buildbot_nix as a python package to buildbot 2023-10-31 11:35:35 +01:00
README.md README: mention oauth credentials 2023-11-17 16:29:28 +01:00

Buildbot-nix

A nixos module to make buildbot a proper Nix-CI.

For an example checkout the example and the module descriptions for master and worker.

This project is still in early stage and many APIs might change over time.

Github

We currently primarly support Github as a platform but we are also looking into supporting other CIs such as gitea.

Buildbot requires a GitHub app, to allow login for GitHub users to its dashboard. After installing the app, create oauth credentials and set them in the buildbot-nix nixos module.

Furthermore buildbot requires a github token with the following permissions:

  • admin:repo_hook, public_repo, repo:status

For github organisations it's recommend to create an additional GitHub user for that.

Real-worlds deployments