Buildbot for Nix, tailored for Lix usecases
Find a file
dependabot[bot] e476849f72 Bump cachix/install-nix-action from 23 to 24
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 23 to 24.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/v23...v24)

---
updated-dependencies:
- dependency-name: cachix/install-nix-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2023-12-04 01:50:18 +00:00
.github Bump cachix/install-nix-action from 23 to 24 2023-12-04 01:50:18 +00:00
buildbot_nix retry git clonning errors 2023-12-03 15:10:16 +00:00
examples make evalWorkerCount configurable 2023-11-12 07:23:35 +01:00
nix drop nix_update_flake_config pipeline 2023-12-03 15:10:16 +00: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-12-03 01:46:52 +00:00
flake.nix move nixpkgs back to nixos-unstable-small 2023-11-20 09:44:19 +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