Figure out how to run the CI stuff in the new repo #6

Open
opened 2026-08-10 11:53:14 +00:00 by dexterlb · 1 comment
Member

The old fazantix repo used CI for the following:

  • running nix flake check which in turn runs all possible linters and checkers to make sure the code is fit for merging (this was done with github actions) - the .github dir should now be removed, and another CI-thing should be used to run this command and block code from merging if it does not succeed
  • building debian packages - this was done with circleci, and should probably be done differently now

Apparently Forgejo has a thing called Actions that could possibly be used, but @gerry should say if this is possible/feasible/wanted to do on the fosdem forgejo server

The old fazantix repo used CI for the following: - running `nix flake check` which in turn runs all possible linters and checkers to make sure the code is fit for merging (this was done with github actions) - the .github dir should now be removed, and another CI-thing should be used to run this command and block code from merging if it does not succeed - building debian packages - this was done with circleci, and should probably be done differently now Apparently Forgejo has a thing called Actions that could possibly be used, but @gerry should say if this is possible/feasible/wanted to do on the fosdem forgejo server
Owner

I have just configured woodpecker ci.
see eg:
#9

Both running checks and building debian packages should be possible. Debian packages can also be pushed to forgejo packages.

https://woodpecker-ci.org/docs/usage/intro
Basically you start with a checkout of your repository which is mounted inside containers where you can then run different commands.
The workspace folder is kept between runs, so you can keep state there.

I have just configured woodpecker ci. see eg: https://git.fosdem.org/video/fazantix/pulls/9 Both running checks and building debian packages should be possible. Debian packages can also be pushed to forgejo packages. https://woodpecker-ci.org/docs/usage/intro Basically you start with a checkout of your repository which is mounted inside containers where you can then run different commands. The workspace folder is kept between runs, so you can keep state there.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
video/fazantix#6
No description provided.