We added some deployment actions, namely to push to Cachix and to GitHub pages. You can check this out in the documentation and you can take a look at typhon-self-config as an example that uses both.
We created typhon-github-action, so that you can start using Typhon’s actions without deploying your own Typhon instance.
But most importantly we opened a Zulip instance, where you can come to ask for help and where I will probably continue posting semi-regular updates like this one.
I am not sure that I will keep this thread updated unless there is some big piece of news like a first release, as I don’t want to create spam.
Thank you everyone for the feedback, and I hope I will discuss the design of Typhon with some of you on Zulip!
@Marcc The webhook system in Typhon just exposes an API endpoint for each project and passes any POST request that is sent to it to a user-defined action that can in turn send commands to Typhon to create jobsets. Thus as long as you can send POST requests from your forge, you can trigger builds automatically! (in theory… atm you’ll have to do some manual work because of Evaluation is not triggered on new jobsets · Issue #3 · typhon-ci/typhon · GitHub)
You can’t currently retreive build results via SSH, but you can expose them over HTTP! Thanks to the discrete (meaning undocumented) feature that distributes store paths from the API when passthru.typhonDist = true; is set in you job’s derivation.
Zulip seemed like a good solution to have easy access to conversation logs. I personally hate Matrix for this, just scrolling up a few messages is an awful thing to do on Element. I am open to the idea of maintaining a bridge, depending on how much work and resources it requires.
Gitea and cachix support looks great and shows how we can add forgejo and attic story!
lib.gitea.mkProject can be used with forgejo, as it is still a soft fork of gitea and is completely backwards compatible (I actually test Gitea support on codeberg.org)!
I have my complaints about matrix as well, but also don’t have a zulip account and don’t really want another chat service if I can avoid it. I think it’s important to go where the community is, and for better or worse it’s Matrix for the Nix community.
So I’ve just deployed my own typhon instance and put one of my github repository under the typhone instance as CI. However, the job always fails on evaluation. On the web interface, it just says Failure on the Nix evaluation status and I don’t really know where I should look to find out more information why the evaluation would fail. Any clue where I should take a look? By the way, the repo could be built successfully outside of typhon.